On Wed, Jan 18, 2012 at 03:36:04PM +0100, Rogier wrote: > > > 32-bits userspace on 64-bits kernel. > > > I assume that's the same from a build-point-of-view ? > > > > I bet it works if you build using "linux32 dpkg-buildpackage -b". > > Never heard of that... > Thanks for educating me. (but, even if I had known of 'linux32', I > doubt I would have suspected that to be the cause). > > I'll try it tonight (the build takes rather long on my machine). > > If my understanding is correct (the manual page says it only affects > the output of uname -m), it implies that the detected kernel > architecture is used to make decisions about the desired or applicable > userspace architecture ? To me, it seems this is not quite Right ? > > Anyway, I assume this will solve it for me.
I think your setup makes the build system assume you are cross-compiling, which you really aren't, but triggers using uname. Please check what the build-xulrunner/config/autoconf.mk file says about TARGET_CPU when building without linux32. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org