** Changed in: linux (Ubuntu)
Status: Confirmed = Won't Fix
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433809
configured the compiler as suggested for my trusty tests, so that I
don't see this build failure anymore in trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433809
Title:
linux build failure
We'll aim to fix this in the kernel. It's a long-held assumption in the
64-bit code that 32-bit also exists, so teasing it all apart will take
some work, all mechanical but time consuming. In the short term it might
be best to just re-enable 32-bit in the toolchain.
--
You received this bug
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433809
Title:
linux build failure seen building 32bit user space support on ppc64el
To manage notifications about this
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) = Andy Whitcroft (apw)
** Changed in: linux (Ubuntu)
Milestone: None = ubuntu-15.03
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Andy Whitcroft (apw)
--
You received this bug notification because you are a
arch/powerpc/Makefile has:
HAS_BIARCH := $(call cc-option-yn, -m32)
but in vivid:
$ gcc-4.8 -m32 -c foo.c
foo.c:1:0: error: -m32 not supported in this configuration
$ gcc-4.9 -m32 -c foo.c
foo.c:1:0: error: -m32 not supported in this configuration
$ gcc-5 -m32 -c foo.c
foo.c:1:0: error:
It does seem a bit pointless to be building a 32-bit vdso on powerpc64le
where you know there is no 32-bit user runtime.
Now if some other part of the kernel needs to be compiled 32-bit, then it would
appear that gcc will need to be configured with
--enable-targets=powerpcle-linux
