Actually, I was wrong about arm-linux-gnueabihf-gcc! It *also* doesn't
find /usr/include/asm, instead correctly finding /usr/arm-linux-
gnueabihf/include/asm!
So actually, as far as I can tell *nothing* uses /usr/include/asm.
--
You received this bug notification because you are a member of Ubun
Can someone please explain why /usr/include/asm is needed? It seems to
me neither gcc -m32 nor gcc -m64 use it (both finding the ones in
/usr/include/i386-linux-gnu and /usr/include/x86_64-linux-gnu instead).
arm-linux-gnueabihf-gcc finds it which is not correct, but can be fixed
easily enough by
This is what worked for me, to build x86_32, x86_64, ARM and ARM64 UEFI
drivers from a single Ubuntu 20.04 platform (which is actually an
AppVeyor build environment):
sudo update-alternatives --remove-all gcc
sudo update-alternatives --remove-all g++
sudo update-alternatives --install /usr/bin/gcc
I have faced the issue trying to cross-compile qt webengine using
arm-linux-gnueabihf-.
during the build process there is an attempt to build a tool for build machine
with `-m32` flag which is failed due to missing `/usr/include/asm/`.
--
You received this bug notification because you are a mem
One (working ?) alternative we've successfully used here to workaround
this weird game of whack-a-mole is to stop relying on gcc-multilib, and
start using :i386 versions of packages. So for instance, we would
install for example the following list of packages on an amd64 machine:
build-essential g
I can confirm that this bug appears in Debian testing too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300211
Title:
Can't install both gcc-multilib and gcc-arm-linux-gnueabihf
To manage notific
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gcc-defaults (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300211
Title:
mcclary states that having /usr/include in the header search path
doesn't prevent the inclusion of wrong header files. He then describes
a system how to layout files to install multiple native and cross
compilers, and how to select defaults. He doesn't talk about the
include paths for these setup
Please see my post #23, stating why this bug is, in my opinion, valid
and (as requested) proposing a solution.
** Changed in: gcc-defaults (Ubuntu)
Status: Opinion => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Please see my post #23, stating why this bug is, in my opinion, valid
and (as requested) proposing a solution.
** Changed in: gcc-defaults (Ubuntu)
Status: Invalid => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
> > ... The problem packages are:
> >
> > gcc-multilib which provides:
> > /usr/include/asm
>
> > For the multiarch configurations, the cross compilers have /usr/include in
> > the search path.
> > Having the symlink there lets the arm cross compiler find the x86 asm
> > headers.
With respect,
grog, this does not work for me on 16.04.
# apt remove binutils
[...]
The following packages will be REMOVED:
binutils binutils-arm-linux-gnueabi build-essential clang clang-3.8 dpkg-dev
g++ g++-5 g++-5-multilib g++-multilib gcc gcc-5 gcc-5-multilib gcc-multilib
lcov
0 upgraded, 0 newly inst
If I understood these comments correctly, the proper workaround is to
remove gcc-multilib and create symlinks manually?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300211
Title:
Can't install bot
Maybe this will provide clues to the problem.
USING ubuntu 16.04
I couldn't install both cpp-arm-linux-gnueabihf and
gcc-4.8-multilib-arm-linux-gnueabihf. I also see other errors.
After following a chain of can't installs I got to binutils which wanted a
version which was conflicting with what wa
this is a bug tracker, not a fan boy forum. If you need incoherent
cross build environments including setups involving both multilib and
multiarch, then don't install gcc-multilib, but provide the correct
include paths on your own. Or use chroots if you don't need these archs
for the same project
Another "me too".
My development evironment requires me to compile code for ARM32, ARM64,
x86-32 and x86-64. How can this be supported?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300211
Title:
Matthias: "Otoh, I don't understand why you would need gcc-multilib and
other cross compilers at the same time."
Not to be a smart-alec, but... so that we can compile for x86_32,
x86_64, and ARM on the same system.
I've just run into this as well while updating build servers from 12.x
to 15.x. I
On 06.04.2016 19:47, T Parys wrote:
> Perhaps the symlink at /usr/include/asm is better suited elsewhere?
>
> The cpp include path for i386 (-m32 flag), is as follows:
>
> foo ~ $ gcc -m32 -Wp,-v test.c
> ignoring nonexistent directory "/usr/local/include/i386-linux-gnu"
> ignoring nonexistent dire
Perhaps the symlink at /usr/include/asm is better suited elsewhere?
The cpp include path for i386 (-m32 flag), is as follows:
foo ~ $ gcc -m32 -Wp,-v test.c
ignoring nonexistent directory "/usr/local/include/i386-linux-gnu"
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-linux-gnu/4.8/../..
But _why_ does gcc-multilib create that link?
gcc-multilib is a meta-package. None of the components that actually do
anything depend on it. If I remove it and keep just the versioned
packages (gcc-5-multilib, g++-5-multilib – or just the appropriate :i386
libraries), gcc/g++ still compile with bo
I would need this too. Being able to compile for x86_64 and armhf at the
same time should be possible.
Any idea how to solve this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300211
Title:
Can't
On 15.10.2015 20:46, Anatol Pomozov wrote:
> I see this problem as well. I need gcc-multilib for some proprietary
> software and arm64 gcc for my project. The fact that Ubuntu does not
> allow to install these 2 packages is rather annoying.
>
> For me it sounds like a bug with packaging. Other dist
I see this problem as well. I need gcc-multilib for some proprietary
software and arm64 gcc for my project. The fact that Ubuntu does not
allow to install these 2 packages is rather annoying.
For me it sounds like a bug with packaging. Other distros (like Linux
Arch) allow to install both packages
> Quite frankly, Canonical are being rather pig-headed about this one.
please respect the code of conduct:
http://www.ubuntu.com/about/about-ubuntu/conduct
Just installing other cross compilers while keeping the wrong asm
headers in the search path doesn't solve the problem.
--
You received thi
Quite frankly, Canonical are being rather pig-headed about this one. Just
install the Linaro compilers from here and you are good to go:
https://www.linaro.org/downloads/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
> I don't think this is true. The problem packages are:
>
> gcc-multilib which provides:
> /usr/include/asm
For the multiarch configurations, the cross compilers have /usr/include
in the search path. Having the symlink there lets the arm cross compiler
find the x86 asm headers.
** Changed in: g
I don't see why this is being marked as invalid. For doing cross
platform development being able to produce 32 and 64 bit on x86 and arm
are needed.
If the work around is just a matter of symlinks then sure this can be
fixed?
** Changed in: gcc-defaults (Ubuntu)
Status: Invalid => Confirme
A workaround for me was to create the symbolic link from
/usr/local/include/asm to /usr/include/x86_64-linux-gnu/asm
instead of (as supplied by gcc-multilib
/usr/include/asm to /usr/include/x86_64-linux-gnu/asm
If this will be the default the packages won't conflict as arm-gcc does
not look in /us
there is nothing enlightening in comment #3
** Changed in: gcc-defaults (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300211
Title:
Can't install both gcc-mu
Re-opening based on comment #3
** Changed in: gcc-defaults (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300211
Title:
Can't install both gcc-multilib and gc
I don't think this is true. The problem packages are:
gcc-multilib which provides:
/usr/include/asm
/usr/share/doc/gcc-multilib
And the following 3 arm packages:
gcc-4.8-arm-linux-gnueabihf which provides
/usr/bin/arm-linux-gnueabihf-gcc-4.8
/usr/bin/arm-linux-gnueabihf-gcc-ar-4.8
/usr/bin/arm-l
this is intended. The gcc-multilib package contains the
/usr/include/asm symlink which breaks the search paths for cross
compilers.
** Changed in: gcc-defaults (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Package changed: ubuntu => gcc-defaults (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300211
Title:
Can't install both gcc-multilib and gcc-arm-linux-gnueabihf
To manage notifications
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
34 matches
Mail list logo
