From: Jeff Sturm <jsturm@one-point.com>
To: Christophe Lyon <christophe.lyon@st.com>
Cc: gcc@gcc.gnu.org
Subject: Re: gcc-3.1 build fails on Solaris-2.7 with --with_gnu_ld
Date: Thu, 25 Jul 2002 05:43:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0207242321320.21240-100000@ops2.one-point.com> (raw)
In-Reply-To: <3D3EA281.20EA0224@st.com>
On Wed, 24 Jul 2002, Christophe Lyon wrote:
> /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!
That's what LD_LIBRARY_PATH_64 is for, however...
> Is this a know bug, or am I doing something wrong?
...I suspect a binutils bug. The incompatible library should be skipped.
You could try a newer binutils, or build with Sun's as/ld, or disable
multilibs.
Jeff
prev parent reply other threads:[~2002-07-25 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 12:33 Christophe Lyon
2002-07-25 5:43 ` Jeff Sturm [this message]
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=Pine.LNX.4.44.0207242321320.21240-100000@ops2.one-point.com \
--to=jsturm@one-point.com \
--cc=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).