From: Douglas Houston <dhouston@staffmail.ed.ac.uk>
To: gcc-help@gcc.gnu.org
Subject: Problems building gcc
Date: Wed, 27 Jul 2016 08:17:00 -0000 [thread overview]
Message-ID: <20160727084755.73846m6y070c2lss@www.staffmail.ed.ac.uk> (raw)
Hi all,
I'm having some trouble installing the latest gcc (which I need to
build another program called Gromacs).
I am on Scientific Linux release 6.8 (Carbon) (kernel
2.6.32-573.3.1.el6.x86_64), trying to install gcc-5.4.0.
After installing the latest gmp, mpfr and mpc, I create a separate
objdir build/install directory as recommended. In there, as root, I run:
../gcc-5.4.0/configure
Which fails with:
/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.
So as directed by the output, I try:
../gcc-5.4.0/configure --disable-multilib
Now it fails with:
checking for x86_64-unknown-linux-gnu-gcc...
/root/gcc-5.4.0-install/./gcc/xgcc
-B/root/gcc-5.4.0-install/./gcc/
-B/usr/local/x86_64-unknown-linux-gnu/bin/ -B/u
sr/local/x86_64-unknown-linux-gnu/lib/ -isystem
/usr/local/x86_64-unknown-linux-
gnu/include -isystem /usr/local/x86_64-unknown-linux-gnu/sys-include
checking for suffix of object files... configure: error: in
`/root/gcc-5.4.0-ins
tall/x86_64-unknown-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
Can anyone suggest what the fix might be? I've looked in config.log as
the output suggests but can't find any reference to
x86_64-unknown-linux-gnu-gcc.
cheers,
Doug
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
next reply other threads:[~2016-07-27 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 8:17 Douglas Houston [this message]
2016-07-27 8:22 ` Jonathan Wakely
2016-07-27 8:33 ` Jonathan Wakely
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=20160727084755.73846m6y070c2lss@www.staffmail.ed.ac.uk \
--to=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).