From: Frank T. <fra...@gm...> - 2012-07-03 17:25:30
|
Oh. I missed that. I have not needed to build Basilisk II in a while. On Tue, Jul 3, 2012 at 12:19 PM, Robert Munafo <mr...@gm...> wrote: > No, Frank, not SheepShaver. BasiliskII. Read the original question again. > > SheepShaver has a different JIT (it targets PowerPC rather than 68K) > and thus manages to avoid the CMOV problem. > > On 7/3/12, Frank Trampe <fra...@gm...> wrote: > > cambridge:~ admin$ file /Applications/SheepShaver-2.3/Support/SheepShaver > > /Applications/SheepShaver-2.3/Support/SheepShaver: Mach-O 64-bit > executable > > x86_64 > > > > I was able to do this on Snow Leopard early this year, I believe. It may > be > > that you did not have 64-bit versions of the dependencies installed when > > you tried to build in 64-bit mode. Do you use MacPorts? > > > > On Tue, Jul 3, 2012 at 6:30 AM, Ronald P. Regensburg > > <ron...@xs...>wrote: > >> I noticed the commit "Use clip_macosx64.mm for BasiliskII 64-bit builds > >> too." > >> > >> However, I have never been able to build a working 64-bit BasiliskII > >> MacOSX. And as far as I know, no one has. > >> > >> In Snow Leopard I can build a 32-bit BasiliskII fine. Attempts to build > a > >> 64-bit application result at best in a x86_64 application that crashes > on > >> launch. > >> > >> Can a 64-bit BasiliskII MacOSX be build from current source? If so, how? > > -- > Robert Munafo -- mrob.com > Follow me at: gplus.to/mrob - fb.com/mrob27 - twitter.com/mrob_27 - > mrob27.wordpress.com - youtube.com/user/mrob143 - rilybot.blogspot.com > |