Re: mipsel -m64 testing
+++ Michael R. Crusoe [2015-05-27 20:19 +0000]:
> Hello,
>
> With regards to the FTBFS below, is Debian mipsel always 64 bit, always 32 bit,
> or a mix?
mipsel (and mips) are 32-bit ABIs. mips64el (and mips64) are the debian
names for the 64-bit ABIs.
> How would I test that?
dpkg-architecture -amipsel -qDEB_HOST_ARCH_BITS
> From: Andreas Tille <andreas@an3as.eu>
>
> Hi Michael,
>
> On Wed, May 27, 2015 at 01:37:30PM +0000, Michael R. Crusoe wrote:
> > I interpret '-m64' as a signal that the developer only supports 64 bit
> > OSes/hardware. From what I can find, mipsel can be 32 or 64bit. So I would
> > suggest removing mipsel from the supported architecture series.
'gcc -m64' (on mipsel) is multilib speak for gcc-mips64el-linux-gnuabi64
Debian should be fixing up these multilib shortcuts because they are
not consistent between architectures. '-m64' means different things on
different arches. Using an explicit GNU triplet in toolchain invocations will
always work both natively and for crossing.
See https://wiki.debian.org/ToolChain/Cross#Multiarch_vs_Multilib
> > Does that make sense?
>
> Not really since it also fails on arm64 with the same error.
adding -m64 on arm64 to a gcc invocation will result in an error
because it is meaningless. In general we should (IMHO) simply not be
using -m32 or -m64 in debian builds.
Not sure if I have understood you properly there? Maybe there is some
other reason for the build failure.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
Reply to: