tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: ${LD} incorrectly rewritten

Julio Merino writes:
 > On Mon, Feb 07, 2011 at 05:06:23PM +0100, Benny Siegert wrote:
 > > On Mon, Feb 7, 2011 at 16:36, Brook Milligan 
 > > <> wrote:
 > > > I was afraid of that. ?So, where do we get the correct path to ld for
 > > > the substitution? ?Or should it be substituted with the value of
 > > > ${LD}, which at least for NetBSD is simply ld?
 > > 
 > > Why have a path there at all? LD=ld should be safe, no?
 > It makes the behavior of the tools not predictable because they rely on the
 > PATH.  I.e. a particular tool was built against a known-working ld binary
 > but a user may suffer apparently random errors if his PATH points to a
 > different (and broken/incompatible) ld.

Which is why I was interested in including the full path.  However, I
cannot find anywhere in pkgsrc that defines the path to ld.  There are
things like ${CCPATH} and ${CPPPATH}, but no ${LDPATH}.

Is ${LDPATH} something that should be added to pkgsrc or is ${LD},
i.e., without a path, ok for this substitution?


Home | Main Index | Thread Index | Old Index