* Peter Pentchev <r...@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 childprocesses 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:\...@echo LDFLAGS=\\"$$LDFLAGS\\"' > Makefile $ unset LDFLAGS $ make LDFLAGS="" $ export LDFLAGS=bar # set by evil dpkg-buildpackage $ make LDFLAGS="foo" -- Jakub Wilk
signature.asc
Description: Digital signature
