Control: tag -1 wontfix
Control: close -1

On Tue, Aug 08, 2017 at 09:36:27PM -0400, James Cowgill wrote:
> I noticed this build of ffmpeg in buster failed on armhf, while the same
> version does build in the unstable version:
> The configure log contains
> > Mon Aug  7 07:36:24 UTC 2017  I: Starting 1st build on remote node 
> > jtx1b-armhf-rb.debian.net.
> [...]
> >  *** standard ***
> > install prefix            /usr
> > source path               /build/ffmpeg-3.3.3
> > C compiler                gcc
> > C library                 glibc
> > ARCH                      aarch64 (generic)
> 
> While I don't know for certain, my guess is that this is an aarch64
> machine doing armhf builds, and the personality in the chroot has not
> been set correctly for armhf. I don't know if pbuilder has this ability
> (I know schroot does), but if not then you could use "setarch linux32"
> instead.

That's the case indeed, and afaik it's not the only case.
I talked a bit with my peers, and there is a consensus on our side that
thing should not be relying on `uname` to detect the host architecture.
Indeed before the stretch release we were actively testing varying
kernel on the i386 builds by using an amd64 kernel and filed bugs for
them.

Please make your package not rely on uname.

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature

Reply via email to