Re: --whole-archive with pgcc

[Gary V. Vaughan]

Hallo Peter,

Peter O'Gorman wrote:
> Gary V. Vaughan wrote:
>> Peter O'Gorman wrote:
>>
>>> Index: ChangeLog
>>> 2005-02-24  Peter O'Gorman  <address@hidden>
>>>
>>>     * libtool.m4 (AC_LIBTOOL_PROG_LD_SHLIBS): The Portland group's
>>>     compiler does not pass --whole-archive. Move gnu ld check for
>>>     the flag to the top so it can be overridden.
>>>     (AC_LIBTOOL_LANG_CXX_CONFIG): Unset whole_archive_flag_spec for
>>>     the portland group's c++ compiler too.
>>>     Reported by Jeff Squyres <address@hidden>
> 
> I was just trying to forward port this and then commit them all together
> when I came across a problem (actually two, but the first one involves
> you :-p)
> 
> This patch was committed to HEAD:
> 2004-11-14  Gary V. Vaughan  <address@hidden>
> 
>         * m4/libtool.m4 (_LT_LINKER_SHLIBS): Typo: s/--rpath/-rpath/g.
>         (_LT_LANG_CXX_CONFIG): Ditto.
> 
> The other problem was a bug in my patch, I unset
> hardcode_libdir_flag_spec_ld instead of hardcode_libdir_flag_spec.
> 
> Anyway, my main problem is --rpath, I see it all over the place on
> branch-1-5, and it is even used in this patch. Is there a problem with
> it?

http://lists.gnu.org/archive/html/libtool-patches/2004-11/msg00039.html

> Why is the above patch only on HEAD? --rpath appears in branch-2-0 too.

branch-2-0 is stable!  --rpath only causes a repeated flags on linux,
with pkgconfig (since pkgconfig uses -rpath), so --rpath for other arches
and non-gnu ld is perfectly fine (and expected!).

On HEAD, when you merge, I'd like to continue to use -rpath for GNU ld
though.  Thanks for the heads up.  And apologies for the crappy
ChangeLog entry.

Cheers,
        Gary.
-- 
Gary V. Vaughan      ())_.  address@hidden,gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook

signature.asc
Description: OpenPGP digital signature