From: Christophe Lyon <christophe.lyon@st.com>
To: gcc@gcc.gnu.org
Subject: gcc-3.1 build fails on Solaris-2.7 with --with_gnu_ld
Date: Wed, 24 Jul 2002 12:33:00 -0000 [thread overview]
Message-ID: <3D3EA281.20EA0224@st.com> (raw)
Hi,
I am trying to install gcc-3.1 on a Sparc/Ultra 60 under
Solaris 2.7 using the --with-gnu-ld switch at configure time.
The build process fails when configuring in
sparc-sun-solaris2.7/sparcv9/libiberty
Configure reports:
configure: error: installation or configuration problem: C compiler
cannot create executables.
and the config.log says:
configure:2212: /tmp/pkg-build-gnumgr/gcc-3.1/gcc-3.1/gcc/xgcc
-B/tmp/pkg-build-gnumgr/gcc-3.1/gcc-3.1/gcc/
-B/apa/gnu/SunOS5.7/.package/gcc-3.1/sparc-sun-solaris2.7/bin/
-B/apa/gnu/SunOS5.7/.package/gcc-3.1/sparc-sun-solaris2.7/lib/ -isystem
/apa/gnu/SunOS5.7/.package/gcc-3.1/sparc-sun-solaris2.7/include
-L/tmp/pkg-build-gnumgr/gcc-3.1/gcc-3.1/ld -m64 -o conftest -O2 -O2
conftest.c 1>&5
/usr/lib/libdl.so.1: could not read symbols: Invalid operation
Indeed, I think it should read /usr/lib/sparcv9/libdl.so in that case.
Playing with LD_LIBRARY_PATH can solve this issue, but I don't really
want /usr/lib/sparcv9 to be first in my $LD_LIBRARY_PATH all the time!
(and if I do so, configuration of libiberty would fail earlier).
I have found similar questions over the www, but no reply :-(
Is this a know bug, or am I doing something wrong?
(I am using ld from binutils-2.11.2)
Regards,
Christophe.
next reply other threads:[~2002-07-24 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 12:33 Christophe Lyon [this message]
2002-07-25 5:43 ` Jeff Sturm
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=3D3EA281.20EA0224@st.com \
--to=christophe.lyon@st.com \
--cc=gcc@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).