This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: libstdc++.dylib linking problem on Darwin

From: Eric Christopher <echristo at apple dot com>
To: Geoffrey Keating <geoffk at apple dot com>, dan at codesourcery dot com
Cc: Douglas Gregor <doug dot gregor at gmail dot com>, libstdc++ <libstdc++ at gcc dot gnu dot org>, gcc mailing list <gcc at gcc dot gnu dot org>
Date: Thu, 12 Apr 2007 16:43:23 -0700
Subject: Re: libstdc++.dylib linking problem on Darwin
References: <15E1B0AC-9084-4D25-A8D6-ECFCDF788035@osl.iu.edu> <m2irc15jh2.fsf@greed.local>

That said, though, there's something weird going on in your build that
should probably be tracked down.  It didn't happen to me last time I
built...

Here's a patch that fixes it though it doesn't fix the testsuite results yet and is likely not quite what Daniel will want...

Dan?

The basic idea is that the darwin code uses slibdir to set the install name of the library - including full path. Yes, this is dumb, but it's the way that darwin does things at the moment. :(

We're getting slibdir set to null which makes the install name believe that it's rooted at /<name> instead of $(slibdir)/<name>.

-eric

Attachment: Makefile.in.diff.txt
Description: Text document

Follow-Ups:
- Re: libstdc++.dylib linking problem on Darwin
  - From: Daniel Jacobowitz

References:
- libstdc++.dylib linking problem on Darwin
  - From: Douglas Gregor
- Re: libstdc++.dylib linking problem on Darwin
  - From: Geoffrey Keating

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]