Bug#872891: gcc-multilib conflicts with GCC cross toolchains
On Tue, Aug 22, 2017 at 4:11 PM, Matthias Klose <firstname.lastname@example.org> 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 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.
> because the cross toolchain has /usr/include on it's include path, which has
> incompatible header files: /usr/include/asm.
Can't this be configured to something else (eg. /usr/include/foobar/asm ) ?
If I understand OP correctly, the goal is simply to have multiple
compilers installed this seems to work fine for
crossbuild-essential-*, so it would be nice to also have it for
gcc-multilib. Does this means we need a new package:
crossbuild-essential-i386 to get both `gcc -m32 (gcc-i386-linux-gnu)`
and `gcc-aarch64-linux-gnu` installed at the same time ?
Thanks for clarification,