This is the mail archive of the gcc-patches@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: PATCH PING: Build machinery: Set poststage1_ldflags for all builds

From: Ian Lance Taylor <iant at google dot com>
To: Richard Guenther <richard dot guenther at gmail dot com>
Cc: Alexandre Oliva <aoliva at redhat dot com>, gcc-patches at gcc dot gnu dot org
Date: Tue, 30 Nov 2010 07:09:02 -0800
Subject: Re: PATCH PING: Build machinery: Set poststage1_ldflags for all builds
References: <mcrk4jvn0ma.fsf@google.com> <oraakri9lo.fsf@livre.localdomain> <AANLkTimxkqt47Ycje-CK4buvL1M-iPp_5Gp1Up1qngm=@mail.gmail.com>

Richard Guenther <richard.guenther@gmail.com> writes:

> So you say that it's impossible for distributors to avoid the static
> link?  What happens when I'd do --with-boot-ldflags without argument?
> Are those ldflags appended to the usual ones picking up stage-$prev
> libs or do they replace them?

The top level Makefile uses environment variables to find the dynamic
libraries built in previous stages, not rpaths encoded in the binary, so
I think there is no issue here.

Ian

References:
- PATCH PING: Build machinery: Set poststage1_ldflags for all builds
  - From: Ian Lance Taylor
- Re: PATCH PING: Build machinery: Set poststage1_ldflags for all builds
  - From: Alexandre Oliva
- Re: PATCH PING: Build machinery: Set poststage1_ldflags for all builds
  - From: Richard Guenther

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