From: Andrew Haley <aph@redhat.com>
To: "Ian S. Worthington" <ianworthington@usa.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: make fails on ld: crti.o "no such file", but present in /usr/lib64
Date: Wed, 13 Feb 2008 11:37:00 -0000 [thread overview]
Message-ID: <47B2D663.9060304@redhat.com> (raw)
In-Reply-To: <555mBLVff2734S11.1202851951@cmsweb11.cms.usa.net>
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@redhat.com>
> To: "Ian S. Worthington" <ianworthington@usa.net>Cc: gcc-help@gcc.gnu.org
> 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.
>>
>
>
>
next prev parent reply other threads:[~2008-02-13 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 21:33 Ian S. Worthington
2008-02-13 11:37 ` Andrew Haley [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-13 0:14 Ian S. Worthington
2008-02-12 22:22 Poor Yorick
2008-02-12 20:25 Ian S. Worthington
2008-02-12 20:39 ` Andrew Haley
2008-02-12 17:47 Ian S. Worthington
2008-02-12 17:59 ` Andrew Haley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47B2D663.9060304@redhat.com \
--to=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=ianworthington@usa.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).