You can ignore the DEBUG lines in config.log, it was me trying to trace the problem by editing configure.sh.
The issue happened here: configure.sh:2925: x86_64-linux-gnu-gcc -Wall `dpkg-buildflags --get CFLAGS` -g -O2 conftest.c >&5 x86_64-linux-gnu-gcc: `dpkg-buildflags: No such file or directory x86_64-linux-gnu-gcc: CFLAGS`: No such file or directory cc1: error: unrecognized command line option "-fget" On Mon, Jan 28, 2013 at 1:26 PM, StalkR <sta...@stalkr.net> wrote: > Hi Paul, > > Thanks for the quick reply. Strange then something must be wrong with my > config. > > $ ls -l /bin/sh > lrwxrwxrwx 1 root root 4 May 14 2010 /bin/sh -> bash* > > $ dpkg -l bash > ii bash 4.1-3 > The GNU Bourne Again SHell > > Attached dpkg-buildpackage stdout log and debian/buildtree/config.log > > Thanks for your help, > StalkR > > On Mon, Jan 28, 2013 at 1:19 PM, Paul Slootman <p...@debian.org> wrote: >> On Mon 28 Jan 2013, StalkR wrote: >>> >>> On squeeze, I failed to compile rsync/unstable from source: >>> dpkg-source -x rsync_3.0.9-4.dsc >>> cd rsync-3.0.9 >>> dpkg-buildpackage -rfakeroot -b >>> [...] errors related to compiler not found.. but after a look at >>> config.log it was because not expanding `dpkg-buildflags --get CFLAGS`. >>> I traced that back to debian/rules, where for CFLAGS/LDFLAGS: >>> CFLAGS += `dpkg-buildflags --get CFLAGS` >>> LDFLAGS = `dpkg-buildflags --get LDFLAGS` >>> while for CPPFLAGS: >>> CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS) >> >> Can you send the complete buildlog? I have no problem whatsoever with >> building on squeeze. >> >> What is your default /bin/sh ? >> >> >> Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
