public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Shared libobjc in gcc 3.0.2 doesn't work with "make check"
Date: Wed, 17 Oct 2001 08:46:00 -0000	[thread overview]
Message-ID: <5.1.0.14.2.20011017174410.05fd8810@mail.lauterbach.com> (raw)
In-Reply-To: <20011017081842.A10021@lucon.org>

At 17:18 17.10.2001, H . J . Lu wrote:
>On Wed, Oct 17, 2001 at 09:58:29AM +0200, Franz Sirl wrote:
> > At 08:46 17.10.2001, H . J . Lu wrote:
> > >The ObjC testcase doesn't work at all unless there is libgcc_s.so.1
> > >somewhere available for dynamic linker. It is because the shared
> > >libobjc has libgcc_s.so.1 in DT_NEEDED and the GNU linker treats
> > >it just like dynamic linker. That means ld won't search -L for
> > >libgcc_s.so.1. If there is no libgcc_s.so.1 for dynamic linker,
> > >which happens when you never install gcc 3.x before, all ObjC tests
> > >will fail. For ObjC test, you should use LD_LIBRARY_PATH Or -rpath
> > >for the final link.
> >
> > AFAIR this was fixed in the mainline by:
> >
> > 2001-06-16  Franz Sirl  <Franz.Sirl-kernel@lauterbach.com>
> >
> >          * gccspec.c (lang_specific_driver): If compiling ObjC, add
> >          -shared-libgcc when necessary.
> >          * Makefile.in (gccspec.o): Compile with DRIVER_DEFINES.
> >
> > Hmm, totally forgot about that, it should have gone into 3.0.1 already...
>
>Why not backport it to 3.0.x?

As I said I forgot about it and now it's too late for 3.0.2. I'll put it in 
my queue for 3.0.3.

Franz.

      reply	other threads:[~2001-10-17  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16 23:46 H . J . Lu
2001-10-17  0:58 ` Franz Sirl
2001-10-17  8:18   ` H . J . Lu
2001-10-17  8:46     ` Franz Sirl [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=5.1.0.14.2.20011017174410.05fd8810@mail.lauterbach.com \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl@lucon.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).