Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
New ebuild for Hercules 3.03.
Created an attachment (id=75222) [edit] hercules-3.03.ebuild
Version 3.03.1 is available, see http://www.conmicro.cx/hercules/hercnew.html renaming the ebuild works.
Hercules 3.03.2 will be out soon, as well; the same ebuild will work there as well. Please note that all Hercules information is now at http://www.hercules-390.org .
I'm not sure why but after switching from hercules-3.02 to 3.03.1 I got strange problems when trying to start my debian/s390 system inside hercules, it would not start the existing system (root fs not found) and crashed when trying to format a new dasd-volume during a new installation. After switching back to hercules-3.02 it worked again! So be aware that there might be some problems. On the other hand, this is the first day I look at hercules, so I just might overlook something here.
There's a reported problem with CTC devices, and a fix for a loop in CCKD DASD that will be in 3.03.2, but nothing we know of that might be that...If you could, please post to the hercules-390 mailing list (yeah, I know, Yahoo! Groups sucks) and see if the guy who does that kind of thing has suggestions.
Hercules 3.04 is out. The same ebuild works for 3.03, 3.03.1, and 3.04.
3.04 works fine for me on amd64.
> # Do NOT replace the optimization flags automatically generated by the > # Hercules configure script. While, in general, the Gentoo way is to allow > # the user to specify his own optimization flags, this is not a good idea > # for Hercules. Hercules stresses the gcc optimizer, and will break in > # mysterious ways if its optimization settings are overridden. Ignoring the user's CFLAGS completely will break systems which are binary incompatible with the gcc default options. Also, some other packages which break mysteriously with normal CFLAGS have an option custom-cflags to allow testing anyway. Would something like use custom-cflags || strip-flags and then continuing to use --enable-optimization, except with sanitised flags, be acceptable?
3.0.4 now in portage ... btw Jay, parallel install fails ... looks like the install rules dont account for this