From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Douglas Houston <dhouston@staffmail.ed.ac.uk>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Problems building gcc
Date: Wed, 27 Jul 2016 08:33:00 -0000 [thread overview]
Message-ID: <CAH6eHdRySRKOPFhqto9KXDmCt3ie62RY3SoVk8ekEDDe9Oub5w@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdS+b3Z-L=kcZrujoWt5N9=P_ptewWpx2hG-SrAA2KLUOg@mail.gmail.com>
On 27 July 2016 at 09:20, Jonathan Wakely wrote:
> On 27 July 2016 at 08:47, Douglas Houston <dhouston@staffmail.ed.ac.uk> wrote:
>> /usr/bin/ld: crt1.o: No such file: No such file or directory
>> collect2: ld returned 1 exit status
>> configure: error: I suspect your system does not have 32-bit developement
>> librar
>> ies (libc and headers). If you have them, rerun configure with
>> --enable-multilib
>> . If you do not have them, and want to build a 64-bit-only compiler, rerun
>> confi
>> gure with --disable-multilib.
>
> https://gcc.gnu.org/wiki/FAQ#gnu_stubs-32.h
P.S. for Scientific Linux the missing package that provides the 32-bit
dev environment is glibc-devel.i686
next prev parent reply other threads:[~2016-07-27 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 8:17 Douglas Houston
2016-07-27 8:22 ` Jonathan Wakely
2016-07-27 8:33 ` Jonathan Wakely [this message]
2016-07-27 21:59 ` Brian Drummond
-- strict thread matches above, loose matches on Subject: below --
2024-02-06 17:36 T Rex
2024-02-06 19:22 ` Jonathan Wakely
[not found] ` <CAGmGLoh+Pbo9G9=1sDRXyHTV7-_CkPDOw+JWppn1TuVRXnszcA@mail.gmail.com>
2024-02-06 22:35 ` Fwd: " T Rex
2024-02-07 7:33 ` Jonathan Wakely
2000-10-20 18:44 Problems building GCC jeisen
2000-07-19 2:17 problems building gcc Helfried Tschemmernegg
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=CAH6eHdRySRKOPFhqto9KXDmCt3ie62RY3SoVk8ekEDDe9Oub5w@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=dhouston@staffmail.ed.ac.uk \
--cc=gcc-help@gcc.gnu.org \
/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).