Following a conversation with vapier, i found that the s390x installation puts libgcc_s.so.1 into /lib64, while the rest of the libraries are on /lib. According to him this should be fixed: the s390x gcc claims to have its os multilib dir set to "../lib64" when it should be just ".". this is why gcc-config puts libgcc_so into /lib64/ instead of /lib/.
i've been wondering lately if we shouldn't be using a libdir of "lib64" for s390x. i'd want to check to see what rhel/sles are doing ...
gcc-config-1.7 no longer installs libgcc_s.so in / with split /usr
(In reply to comment #2) > gcc-config-1.7 no longer installs libgcc_s.so in / with split /usr and thats stable now
yes, but our s390x port i think is wrong in that it uses /lib instead of /lib64. it's something we need to fix up in our profiles. should be as simple as adding a new s390x sub-profile i think with the right settings exported ...
i've added default/linux/s390/10.0/server/s390x and live converted lgentoo2 over to that. if you want to change the catalyst builder to start using that for its profile for s390x systems, that'd be good. you shouldn't need to make any other change.
Stages using /lib64(In reply to comment #5) > i've added default/linux/s390/10.0/server/s390x and live converted lgentoo2 > over to that. if you want to change the catalyst builder to start using > that for its profile for s390x systems, that'd be good. you shouldn't need > to make any other change. Done, new stages are in the mirrors.
