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

Re: Debhelper: LDFLAGS

On 19.12.2010 21:17, Jakub Wilk wrote:
> * Peter Pentchev <roam@ringlet.net>, 2010-12-19, 21:59:
>>>> When you say that setting the custom LDFLAGS doesn't work, have you
>>>> actually exported them? :)  If you just do LDFLAGS=... or LDFLAGS
>>>> != ... or LDFLAGS := ..., make(1) will only use the new value
>>>> *within the Makefile itself*, it won't be passed to child
>>>> processes such as the configure script.
>>> This is all true, but I don't think this is the culprit here.
>>> dpkg-buildpackage puts LDFLAGS into environment, so it would be
>>> exported even if you didn't use the "export" keyword.
>> Erm, yes, but dpkg-buildpackage doesn't see the LDFLAGS modified
>> in the rules file either, does it?  If you put into the rules file
>> a line saying "LDFLAGS=-Wl,--as-needed" without the export keyword,
>> it would still not work - that was the point of my explanation,
>> just as you say below :)
> Nah, it would work just fine:
> $ printf 'LDFLAGS=foo\nall:\n\t@echo LDFLAGS=\\"$$LDFLAGS\\"' > Makefile

You missed the point here: the env vars are *not* passed to sub shells. As
configure is a shell script your example will not work. Try substituting echo
with a shell script and run the echo from within the shell script, if you want.


Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: