Hi folks,
I seldom mess with the s390x linux stuff unless something in Hercules has changed or seems buggy etc...
This past week Hercules has changed the Floating Point emulation for the "hardware". I pulled out the old FC11 disk image, ipled and finally got "ucbtest" floating point test suite running. One of the things needed was addition of some defines to the fpu_control.h include file as described in a web post - http://www.eglibc.org/archives/patches/msg00511.html from which I only added the following:
+#define _FPU_RC_NEAREST 0x00 /* RECOMMENDED */ +#define _FPU_RC_DOWN 0x03 +#define _FPU_RC_UP 0x02 +#define _FPU_RC_ZERO 0x01
Since I don't know anything about this stuff I don't know if the "Stub version" of fpu_control.h needs these additional items or if they are correct values defined.
Most of the floating point stuff passed the tests but variations in GCC and glibc can have an effect on results so I cranked up the FC14 disk image and found:
No GCC installed No ssh ability ( maybe this is a daemon which needs to be started but which one ? - it works with the FC11 image ) yum really likes to print a couple of lines and then Hercules belches "illegal instruction" and returns the prompt yum list installed or one of the simple yum commands work but can't install or update gcc or anything else it seems
So to finally get to the end of this stuff, I see FC15 is available but so far no 'turnkey' disk image. If I follow the instructions to build from the page: http://secondary.fedoraproject.org/pub/alt/spins/S390/README where it mentions
"11) Just relax and enjoy the rest of the automated install"
When it is finished do I get a FC11 style image ( ssh, gcc, yum work ) or a FC14 style image ( no gcc, yum problematic, ssh maybe works with something in init.d (?) which needs manual editing ) ?
Phil
Phil,
Which version of Hercules are you using? I imagine if you are using the new FP stuff in hercules you are higher than SVN 7709
I am using SVN 7704 with no issues running FC15 / yum or anything else..
I would shut-down hercules and make a backup copy of the Hercules DASD that you installed FC15 on before continuing so you do not have to go through the install again if things break later.
This Hercules Disk image you created for FC15 hopefully has network connectivity through a CTC or LCS device and has access to the internet. If that is all working correctly - I would do a yum update which should install the updates to the packages you have installed in your system. I ran into a couple of dependency issues with my initial yum update and needed to remove some packages - I needed to remove these packages installed from the FC15 initial which I believe is what you did - These packages are not required on s390x arch
rpm -e gnome-bluetooth
rpm -e gvfs-obexftp
rpm -e gdm-plugin-fingerprint
You should also be able to do a yum install for any packages that that are missing to compile the code using GCC
yum install gcc should pull in these packages
============================================================================ =========================================================
Package Arch Version Repository Size
============================================================================ =========================================================
Installing:
gcc s390x 4.6.0-10.fc15 updates 9.9 M
Installing for dependencies:
binutils s390x 2.21.51.0.6-6.fc15 updates 2.5 M
cloog-ppl s390x 0.15.9-3.fc15 fedora 90 k
cpp s390x 4.6.0-10.fc15 updates 3.6 M
glibc-devel s390x 2.14-5 updates 984 k
glibc-headers s390x 2.14-5 updates 594 k
kernel-headers s390x 2.6.40-4.fc15 updates 740 k
libmpc s390x 0.8.3-0.3.svn855.fc15 fedora 46 k
ppl s390x 0.11.2-1.fc15 fedora 1.4 M
ppl-pwl s390x 0.11.2-1.fc15 fedora 35 k
Transaction Summary
Installed:
gcc.s390x 0:4.6.0-10.fc15
Dependency Installed:
binutils.s390x 0:2.21.51.0.6-6.fc15 cloog-ppl.s390x 0:0.15.9-3.fc15 cpp.s390x 0:4.6.0-10.fc15
glibc-devel.s390x 0:2.14-5 glibc-headers.s390x 0:2.14-5 kernel-headers.s390x 0:2.6.40-4.fc15
libmpc.s390x 0:0.8.3-0.3.svn855.fc15 ppl.s390x 0:0.11.2-1.fc15 ppl-pwl.s390x 0:0.11.2-1.fc15
Complete!
FC15 uses init.d script for legacy startup - but most startup items are controlled through systemd - man systemctl will give you some insight to the newer init.d process used for FC15 - also check this link for additional information on debugging the system startup
http://0pointer.de/blog/projects/systemd-for-admins-1.html
-Phil P.