On 25.10.2012 21:20, Guillem Jover wrote:
> On Thu, 2012-10-25 at 11:53:47 -0700, Jonathan Nieder wrote:
>> Matthias Klose wrote:
>>> A lot of rules files uses loops around configure calls, however there's no
>>> export mode which escapes the spaces in the output. Please add one. The sh
>>> mode
>>> won't work either for this case.
>>
>> Doesn't
>>
>> set -e; \
>> eval "$$(dpkg-buildflags --export=sh)"; \
>> for v in $(versions); \
>> do \
>> ... \
>> done
>>
>> work?
the eval trick does work, however the variables are then passed in the
environment, not on the command line. I don't think it makes a difference for
GNU autoconf, but it might not be appropriate for other build systems.
> Or just “$(shell dpkg-buildflags --export=configure)”? I do not really
> see a problem here. I might be missing something else going on, but
> otherwise I'll be closing this report in a bit.
No. Doesn't work if the call depends on the loop variable.
> (In addition using $(shell) allows to set a variables once per
> Makefile, and not once per loop.)
Right, but that's needed for stuff like
for p in $(filter-out $(PYTHON_DEFAULT), $(PYTHONS)) \
; do \
dh_auto_configure --builddir=$(CURDIR)/debian/build-$$p \
-- \
$(BARE_CONFIG_FLAGS) \
--disable-ruby \
PYTHON=$$p \
$$(DEB_CFLAGS_MAINT_APPEND=$$($$p-config --includes)
dpkg-buildflags --export=configure)"; \
done
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
