I think the most reliable method would be: compile a test program using the configured compiler with default flags (i.e. no -m64, -m32, -mx32), and then run file on the test program. If file outputs "64-bit.*x86-64" then it's amd64; if file outputs "32-bit.*x86-64" then it's x32.
Or, less reliably, you could look at the configure triplet, which is x86_64*linux-gnux32 for x32 builds, and x86_64*linux-gnu for amd64 builds. -- Daniel Schepler On Mon, Sep 8, 2014 at 12:51 PM, Sage Weil <sw...@redhat.com> wrote: > On Fri, 5 Sep 2014, Thorsten Glaser wrote: >> Daniel Schepler dixit: >> >> >> Attached patch fixes this by installing yasm on amd64 only. >> >> >Would this really work without also adding Build-Conflicts: yasm [!amd64]? >> >I >> >> Only if we build in clean chroots. Which we do, always. >> B-C is indeed justified here, though. > > I'll apply the original patch (and backport) to start. But making the > build properly detect amd64 would be even better. Right now we are > testing whether `arch` = 'x86_64'. What should we do to distinguish > between an x86_64 and x32 build? > > Thanks! > sage -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
