Bug 227763 – app-emulation/basiliskII-1.0_pre20060501 (updated) ebuild supersedes BasiliskII-JIT-1.0.0

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Eric "me262" Mason 2008-06-17 08:38:26 UTC]

Referencing bug 185937: http://bugs.gentoo.org/show_bug.cgi?id=185937
Basilisk II was broken by a old baselayout, it has also affected the basilisk-II-jit ebuild, and both do not compile. Digging around, I found that the sources used were Mandriva sources back from 2003, and not the latest from the Basilisk II JIT website (which are 2006). The 2006 sources do compile cleanly, furthermore, it seems that Basilisk and the JIT fork have recombined (the project is called Basilisk II, yet features the UAE DynCPU). The CVS sources on the standard page also seem to have more recent date from January 2008.
I've updated the ebuild for the Basilisk II (2006) on the JIT webpage, instead of the Mandriva JIT (2003) ones.

Reproducible: Always

Steps to Reproduce:

[Comment 1 Eric "me262" Mason 2008-06-17 08:39:03 UTC]

Created attachment 157215 [details]
ebuild for basiliskII-1.0_pre20060501

I'd like this to hit upstream, as it is now the only Basilisk II ebuild that's capable of being built on a Gentoo system recent as of 06/15/2008, and should supersede the basiliskII-jit ebuild (which should probably be removed because it fails to compile).

[Comment 2 Eric "me262" Mason 2008-06-17 08:52:49 UTC]

Created attachment 157219 [details]
ebuild for basiliskII-1.0_pre20060501

I'd like this to hit upstream, as it is now the only Basilisk II ebuild that's
capable of being built on a Gentoo system recent as of 06/15/2008, and should
supersede the basiliskII-jit ebuild (which should probably be removed because
it fails to compile).

[Comment 3 Jeremy Olexa (darkside) (RETIRED) 2008-06-18 00:22:32 UTC]

Maybe this bug solves bug #168872. Not sure..?

[Comment 4 Eric "me262" Mason 2008-06-18 17:33:17 UTC]

Created attachment 157475 [details]
Picture of Basilisk II running System 7.5.5

(In reply to comment #3)
> Maybe this bug solves bug #168872. Not sure..?

As you can see I can run it, along with Escape Velocity on System 7.5.5, and a barebones System 8 image.
Getting my Mac HD installed is another matter. ^_^

You may have a corrupt ROM file, what size are you using? I've been running with my Performa 638 ROM successfully for a while, emulating a Quadra 900 with a 68040.

If it still doesn't work, try running the Windows version under Wine, that was working for me too before I rewrote the ebuild for linux.

[Comment 5 Jeremy Olexa (darkside) (RETIRED) 2008-06-29 02:47:06 UTC]

(In reply to comment #4)
> (In reply to comment #3)
> > Maybe this bug solves bug #168872. Not sure..?
> 
> As you can see I can run it, along with Escape Velocity on System 7.5.5, and a
> barebones System 8 image.
> Getting my Mac HD installed is another matter. ^_^
> 
> You may have a corrupt ROM file, what size are you using? I've been running
> with my Performa 638 ROM successfully for a while, emulating a Quadra 900 with
> a 68040.
> 
> If it still doesn't work, try running the Windows version under Wine, that was
> working for me too before I rewrote the ebuild for linux.

Heh, I'm not looking for help here. I'm just trying to understand this package so I can check it into CVS for you. ;)

I am confused about the relationship with this package and basiliskII-jit - from my understanding they are the same thing. (According to the HOMEPAGE in the ebuild you provided) "Basilisk II 1.0-Pre JIT R5 (01.May.2006)"

If that is the case, I would rather mask app-emulation/basiliskII-jit-1.0.0-r1 and add app-emulation/basiliskII-jit-1.0_pre20060501 to the tree. What do you think?

[Comment 6 Eric "me262" Mason 2008-07-09 05:36:39 UTC]

I did encounter that crash, and figured out how to work around it (it seems to be a software error).
When I wasn't using a disk image (tried hooking the mac hd up directly), I would get this error. Once I had loaded a disk image (any one seems to work, and oddly enough, a dd if=/dev/hda of=/home/user/mac.img works too), I could use the software fine.

(In reply to comment #5)
> I am confused about the relationship with this package and basiliskII-jit -
> from my understanding they are the same thing. (According to the HOMEPAGE in
> the ebuild you provided) "Basilisk II 1.0-Pre JIT R5 (01.May.2006)"

From what I can surmise, the JIT fork must have merged back into the regular repository (or became, it's hard to tell). In short, JIT has become optional in the compile process (which is why I added a JIT use-flag).
I pretty much consider this the homepage now, since the old one is 7 years stale. So if the site still calls itself Basilisk II JIT, then yes, let's just call it basiliskII-jit. The source file comes from this page after all.
 
> If that is the case, I would rather mask app-emulation/basiliskII-jit-1.0.0-r1
> and add app-emulation/basiliskII-jit-1.0_pre20060501 to the tree. What do you
> think?

Great minds think alike!
I myself would actually mask 1.0.0-r1 for removal, since it doesn't compile anymore, and for the reasons listed below:

1. The source archive that 1.0.0-r1 uses is from mandrake/mandriva sources dated to 2003. I took a peek inside the source archive.
2. I also peered into the ebuild (in order to fix it), and the source URL it pulls from is from an AOL homepage. This just sends up all kinds of warnings and security flags for me.

[Comment 7 Jeremy Olexa (darkside) (RETIRED) 2008-07-09 12:37:46 UTC]

Ok.

Assigning to myself so I don't forget about this bug. I'll get to it in the near future.

[Comment 8 Jeremy Olexa (darkside) (RETIRED) 2008-07-17 03:16:39 UTC]

Compiled fine here, small modifications. Thanks for the ebuild. 

Renamed as basiliskII-jit-1.0_pre20060501.ebuild per comment #6.