Hi Daniel! On 11/07/2014 12:00 AM, Daniel Schepler wrote: > I was building on amd64 using pbuilder. As far as I can tell, the > culprit is this in debian/rules:
I see. > # Cross configuration support. Check for an environment variable > # $GDB_TARGET, or a file debian/target. > ifndef GDB_TARGET > DEBIAN_TARGET_FILE := $(strip $(shell cat debian/target 2>/dev/null)) > ifneq ($(DEBIAN_TARGET_FILE),) > GDB_TARGET := $(DEBIAN_TARGET_FILE) > endif > endif > > DEB_TARGET_ARCH := $(shell dpkg-architecture -f \ > -a$(GDB_TARGET) -qDEB_HOST_ARCH 2>/dev/null) > ... > ifeq ($(DEB_TARGET_ARCH),) > $(error GDB_TARGET value "$(GDB_TARGET)" is not a valid Debian architecture) > endif > > So because debian/target doesn't exist in a straight build, GDB_TARGET > is empty. And "dpkg-architecture -f -a -qDEB_HOST_ARCH" prints this > to stderr and nothing to stdout: > dpkg-architecture: unknown option `DEB_HOST_ARCH' > > Use --help for program usage information. > > Therefore, DEB_TARGET_ARCH is empty and the error gets triggered. I agree, dpkg was updated and triggered this bug. On Wheezy: glaubitz@wheezy64:~> lsb_release -c Codename: wheezy glaubitz@wheezy64:~> dpkg-architecture -f -a -qDEB_HOST_ARCH amd64 glaubitz@wheezy64:~> On Jessie/Unstable: glaubitz@z6:~> lsb_release -c Codename: sid glaubitz@z6:~> dpkg-architecture -f -a -qDEB_HOST_ARCH dpkg-architecture: unknown option `DEB_HOST_ARCH' Use --help for program usage information. glaubitz@z6:~> > I suspect this might be new behavior in recent updates of dpkg; but if > it worked before with nothing provided to -a, that would be a pure > accident. Yes. > Could you make sure that your build environment is up to > date with sid and has dpkg 1.17.21? I actually didn't try to build it myself when I first replied to your bug report as my main concern with your bug report was the lack of additional information that was necessary. I actually merely had a look at the buildds and saw the FTBFS on "powerpcspe" and "sh4" only while on the other architectures the builds were successful, so I assumed first it was an issue regarding these two architectures. Turns out, however, the other architectures builds were successful because they are long enough in the past to have been using an older version of dpkg which still accepted a blank argument to the parameter "-a". In any case, I can confirm and reproduce the issue and I agree it's grave. We should probably rename the title of the bug report though such that Hector or anyone else wanting to look into fixing the bug quickly understand the background of this bug. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
