From: Alexandre Oliva <aoliva@redhat.com>
To: Philip Blundell <philb@gnu.org>
Cc: binutils@sources.redhat.com, gcc@gcc.gnu.org
Subject: Re: Wrong dynamic-linker used on Solaris 7/x86
Date: Sun, 20 May 2001 08:32:00 -0000 [thread overview]
Message-ID: <oreltk11f6.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <E151UuD-0005Kv-00@kings-cross.london.uk.eu.org>
On May 20, 2001, Philip Blundell <philb@gnu.org> wrote:
>> correctly even with older versions of GNU ld. Another option is to
>> implement -I as an alias to --dynamic-linker on Solaris; this would
>> allow gcc to use the same LINK_SPEC, but would require a fixed GNU ld.
>> The plus of this option is that one could switch between GNU ld and
>> Solaris ld with -B switches, as it is possible today.
> I think this is the way to go.
Even though it would cause GCC 3.0 to not work with GNU binutils 2.11?
BTW, I've got more news on this issue. Sun does support
/usr/lib/libc.so.1 as the interpreter; the fact that it crashes is
indeed caused by a bug in their code. I'm helping my friend at Sun
correct it. So, it might be that we don't need to fix anything, after
all. The problem would only show up with a NULL environment, so it's
probably not something one would encounter in real life. And then,
hopefully Sun will release a patch to address this problem soon, so
whoever encounters the problem might as well just upgrade, or work
around the problem by telling GNU ld to use /usr/lib/ld.so.1 as the
dynamic linker, or by using Sun ld.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2001-05-20 8:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-20 7:44 Alexandre Oliva
2001-05-20 8:14 ` Philip Blundell
2001-05-20 8:32 ` Alexandre Oliva [this message]
2001-05-20 8:41 ` Philip Blundell
2001-05-20 9:06 ` Alexandre Oliva
2001-05-20 10:25 ` Mark Mitchell
2001-05-20 10:52 ` Alexandre Oliva
2001-05-20 10:57 ` Mark Mitchell
2001-05-20 11:03 ` Alexandre Oliva
2001-05-20 11:08 ` Mark Mitchell
2001-05-20 11:28 ` Alexandre Oliva
2001-05-20 12:01 ` Ulrich Drepper
2001-05-20 11:10 ` Philip Blundell
2001-05-20 12:52 ` Alexandre Oliva
2001-05-20 14:35 ` Philip Blundell
2001-05-20 14:49 ` Alexandre Oliva
2001-05-22 4:58 ` Alexandre Oliva
2001-05-22 5:20 ` Philip Blundell
2001-05-22 7:00 ` Nick Clifton
2001-05-22 7:15 ` Alexandre Oliva
2001-05-22 7:19 ` Philip Blundell
2001-05-20 16:44 ` H . J . Lu
2001-05-20 21:22 ` Mark Mitchell
2001-05-21 9:04 ` H . J . Lu
2001-05-20 23:50 ` Philip Blundell
2001-05-21 8:54 ` H . J . Lu
2001-05-22 3:23 ` Alexandre Oliva
2001-05-22 10:08 ` Matt Schalit
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=oreltk11f6.fsf@guarana.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=philb@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).