Ian S. Worthington wrote:
Thanks Andrew.
I can certainly install the .s390 package and see. I'm concerned though in
case it breaks something. Are they designed to live togther in harmony,
Yes.
and is there any way of testing that before I trash my system?
No, but yum and RPM are designed not to trash your system.
Andrew.
i
------ Original Message ------
Received: Tue, 12 Feb 2008 08:39:17 PM GMT
From: Andrew Haley <aph@xxxxxxxxxx>
To: "Ian S. Worthington" <ianworthington@xxxxxxx>Cc: gcc-help@xxxxxxxxxxx
Subject: Re: make fails on ld: crti.o "no such file", but present in
/usr/lib64
Ian S. Worthington wrote:
Hi Andrew --
Many thanks for your reply.
It looks like I've got glibc-devel installed and (almost) up to date:
# yum list glibc-devel
Setting up repositories
update 100% |=========================| 951 B
00:00
base 1.1 kB
00:00
addons 100% |=========================| 951 B
00:00
extras 100% |=========================| 951 B
00:00
Reading repository metadata in from local files
Installed Packages
glibc-devel.s390x 2.3.4-2.36 installed
Available Packages
glibc-devel.s390x 2.3.4-2.39 base
glibc-devel.s390 2.3.4-2.39 base
Ah, S/390. You shoulda said. :-)
OK, so there are .s390 and .s390x packages. I guess one of these is for
/lib and one of these is for /lib64, but I'm not a S/390 expert. You
only have the .s390x installed.
I've now updated to .39 just in case but still only have that one copy.
/usr/lib doesn't seem to have much in it. Is this correct?
Maybe you really don't want to build the 32-bit libraries, you just
want the 64-bit versions. In that case you can configure with
--disable-multilib.
Andrew.
