Bug#773065: selecting target via dpkg-buildpackage --target-arch
Control: tags -1 + moreinfo
On 12/16/2014 07:58 PM, Helmut Grohne wrote:
> Control: tags -1 - moreinfo
>
> On Tue, Dec 16, 2014 at 01:37:12PM +0100, Matthias Klose wrote:
>> please verify your patch using an old dpkg from wheezy, using native builds and
>> the supported cross builds and attach the four compressed build logs.
>
> I have some problems making sense of this, please clarify:
if you have some problems, then please don't play bts ping pong. the build logs
are not yet attached.
> You are asking me to use an old dpkg. But dpkg-architecture (which is
> what sets DEB_TARGET_ARCH) is in dpkg-dev. So I am assuming that you did
> mean dpkg-dev here. Do you confirm?
>
> When downgrading dpkg-dev to wheezy, any build finishes rather quickly:
>
> | dpkg-checkbuilddeps: Unmet build dependencies: dpkg-dev (>= 1.17.11)
>
> Builds with wheezy dpkg-dev simply are not supported by the packaging.
> Likely, this is not what you wanted to know.
surely you did regenerate the control file for the wheezy build.
> You are mentioning four logs, but I have problems understanding which
> configurations you are asking for. From your two lines, I'd suppose you
> are asking for:
>
> * host=build=target=amd64 (for example) in a sid chroot with dpkg-dev
> downgraded to wheezy. (Fails as above.)
yes, this called native.
> * host=build=amd64 target=x32 with the supported cross build method in
> a sid chroot with dpkg-dev downgraded to wheezy and selecting the
> target via debian/target. (Build-Depends not installable, because
> #771497.)
sure, fix it.
>
> So this is two builds, but you asked for four. Which ones am I missing?
these two using the old and the new dpkg.
Reply to: