Bug#872891: gcc-multilib conflicts with GCC cross toolchains

2021-11-16 Thread Vincent Danjean
Package: gcc-multilib Version: 4:11.2.0-2 Followup-For: Bug #872891 Hi, I also have been hit by this bug. I'm using several cross-tool chains (arm-linux-gnueabi, mipsel-linux-gnu, i686-linux-gnu) and I was wondering why using plain gcc with -m32 does not work. Perhaps due to the fact that g

Bug#872891: gcc-multilib conflicts with GCC cross toolchains

2021-05-04 Thread Matthias Klose
On 5/3/21 10:58 PM, Josh Triplett wrote: > On Mon, May 03, 2021 at 12:56:58PM +0200, Matthias Klose wrote: Is that still the case, a few years later? >>> >>> I'm running into this issue as well. I'd like to be able to >>> cross-compile for aarch64, and I'd also like gcc -m32 to continue >>> wo

Bug#872891: gcc-multilib conflicts with GCC cross toolchains

2021-05-03 Thread Josh Triplett
On Mon, May 03, 2021 at 12:56:58PM +0200, Matthias Klose wrote: > > > Is that still the case, a few years later? > > > > I'm running into this issue as well. I'd like to be able to > > cross-compile for aarch64, and I'd also like gcc -m32 to continue > > working. > > yes, it's still the case. Nobo

Bug#872891: gcc-multilib conflicts with GCC cross toolchains

2021-05-03 Thread Matthias Klose
> > Is that still the case, a few years later? > > I'm running into this issue as well. I'd like to be able to > cross-compile for aarch64, and I'd also like gcc -m32 to continue > working. yes, it's still the case. Nobody is working on that. Note that you can also install gcc-i686-linux-gnu to b

Bug#872891: gcc-multilib conflicts with GCC cross toolchains

2021-04-29 Thread Josh Triplett
On Mon, 21 Sep 2020 22:11:59 +0200 ni...@lysator.liu.se (Niels =?utf-8?Q?M=C3=B6ller?=) wrote: > Hi, > > in 2017, Matthias Klose marked this bug as wontfix, and explained the > problem like this: > > > because the cross toolchain has /usr/include on it's include path, > > which has incompatible

Bug#872891: gcc-multilib conflicts with GCC cross toolchains

2020-09-21 Thread Niels Möller
Hi, in 2017, Matthias Klose marked this bug as wontfix, and explained the problem like this: > because the cross toolchain has /usr/include on it's include path, > which has incompatible header files: /usr/include/asm. Is that still the case, a few years later? I have an x86_64 machine with deb

Bug#872891: gcc-multilib conflicts with GCC cross toolchains

2017-08-22 Thread Mathieu Malaterre
Hi, On Tue, Aug 22, 2017 at 4:11 PM, Matthias Klose wrote: > Control: tags -1 + wontfix > > On 22.08.2017 10:10, Aaron Marcher wrote: >> Package: gcc-multilib >> Version: 4:6.3.0-4 >> >> The package gcc-multilib conflicts with any GCC cross toolchains (for >> example "gcc-aarch64-linux-gnu"). As

Bug#872891: gcc-multilib conflicts with GCC cross toolchains

2017-08-22 Thread Matthias Klose
Control: tags -1 + wontfix On 22.08.2017 10:10, Aaron Marcher wrote: > Package: gcc-multilib > Version: 4:6.3.0-4 > > The package gcc-multilib conflicts with any GCC cross toolchains (for > example "gcc-aarch64-linux-gnu"). As far as I understood it, it is not > possible to build 32-bit binaries

Bug#872891: gcc-multilib conflicts with GCC cross toolchains

2017-08-22 Thread Aaron Marcher
Package: gcc-multilib Version: 4:6.3.0-4 The package gcc-multilib conflicts with any GCC cross toolchains (for example "gcc-aarch64-linux-gnu"). As far as I understood it, it is not possible to build 32-bit binaries on a 64-bit system (using -m32 flag) when a GCC cross toolchain is installed. I a