This may very well be the issue. Thanks for the reply, dann.
I'm running a test build using -Wa,-march... to check if the build
succeeds now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939379
Ti
Here's some discussion from over a decade ago on the topic
https://gcc.gnu.org/pipermail/gcc-patches/2009-May/262656.html (spoiler:
it doesn't really go anywhere)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
FWIW I fixed a similar issue in supertuxkart recently by patching the .S
file to have a ".fpu vfp" directive in it -- although probably ".arch
armv7-a+fp" would have been more appropriate.
It does seem strange that "gcc -march foo bar.s" does not pass -march to
the assembler but I have no real ide
hm.. yeah, I can reproduce:
dannf@xps13:/tmp/php8.1-8.1.0~rc4$ arm-linux-gnueabihf-gcc -IZend/asm/
"-I/tmp/php8.1-8.1.0~rc4/Zend/asm/" "-I/tmp/php8.1-8.1.0~rc4/ext-build/include"
"-I/tmp/php8.1-8.1.0~rc4/ext-build/main" "-I/tmp/php8.1-8.1.0~rc4"
"-I/tmp/php8.1-8.1.0~rc4/ext-build/ext/date/lib"
php-swoole on armhf impish is also affected:
https://launchpad.net/~ondrej/+archive/ubuntu/php/+build/22393235
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939379
Title:
ARM kernel builds fail wit
On Wednesday, November 10 2021, Matthias Klose wrote:
> $ arm-linux-gnueabihf-gcc-11 -march=armv7-a+fp -c -x c /dev/null ; echo $?
> 0
>
> that works, contrary what is mentioned in comment #14
I don't understand your statement here. I never claimed that gcc-11
"doesn't work". I never claimed th
** Changed in: php8.1 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939379
Title:
ARM kernel builds fail with GCC 11
To manage notifications about this bu
$ arm-linux-gnueabihf-gcc-11 -march=armv7-a+fp -c -x c /dev/null ; echo $?
0
that works, contrary what is mentioned in comment #14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939379
Title:
ARM k
I've added php8.1 as a task because this bug is affecting the package as
well.
FWIW, I wasn't able to workaround this problem by just using
-march=armv7-a+fp, even though I agree it should have worked. I had to
actually pass -mfpu=vfpv3-d16 (no need to pass -march).
Either way, I just wanted to
** Also affects: php8.1 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939379
Title:
ARM kernel builds fail with GCC 11
To manage notifications
@juerg
From your autopkgtest result:
Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.13.0-1006-raspi -C
/lib/modules/5.13.0-1006-raspi/build
M=/var/lib/dkms/adv-17v35x/5.0.6.0-1/build
cleaning build area...
DKMS: build completed.
Building module:
cleaning build area...
ma
> $ arm-linux-gnueabihf-gcc-11 -march=armv7-a -c -x c /dev/null
> cc1: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU
you have to use -march=armv7-a+fp for now on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
this log shows:
make: Entering directory '/usr/src/linux-headers-5.13.0-14-generic'
CC [M] /var/lib/dkms/adv-17v35x/5.0.6.0-1/build/adv17v35x.o
please could you provide a verbose build, show the exact invocation of
the compiler?
--
You received this bug notification because you are a member
We're also seeing dkms build failures on armhf due to this:
https://autopkgtest.ubuntu.com/results/autopkgtest-
impish/impish/armhf/a/adv-17v35x/20210825_233224_cd9ac@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Juerg, that fun is from bug 1939973
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939379
Title:
ARM kernel builds fail with GCC 11
To manage notifications about this bug go to:
https://bugs.launch
On Fri, Aug 13, 2021 at 7:35 AM Juerg Haefliger
<1939...@bugs.launchpad.net> wrote:
>
> I wonder if this is related but cpio on impish arm64 seems broken.
I wouldn't think so - this change should only impact armhf.
-dann
--
You received this bug notification because you are a member of Ubuntu
I wonder if this is related but cpio on impish arm64 seems broken. All
my kernel builds on impish fail when cpio is invoked. In a hirsute arm64
chroot:
(hirsute-arm64)ubuntu@seidel:~$ find foo/ -print | cpio -pd
--preserve-modification-time
$(pwd)/00112233
yes, that's what is supposed to do, but apparently it's not doing
that. Now configured with --with-fpu=vfpv3-d16 again, which lets the
boost build at least succeed again.
Still need to figure out if we need to re-upload packages built after
the gcc-defaults change and before the gcc fix.
--
Yo
Interesting - here's what I see in the boost1.74 log:
"g++" -x assembler-with-cpp -fPIC -pthread -O3 -finline-functions
-Wno-inline -Wall -g -fvisibility=hidden -Wdate-time -D_FORTIFY_SOURCE=2
-DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_DYN_LINK=1 -DBOOST_CONTEXT_SOURCE
-DBOOST_DISABLE_ASSERTS -DNDEB
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gcc-11 (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/1939379
Title:
ARM
Oh, I've seen this in some other packages too (boost1.74 was one I
think). Do we need to change dpkg to have different default CFLAGS or
something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939379
Yeah, I think what's going on is that - due to the above change - gcc-11
no longer enables an FPU independently of the selected arch. The FPU is
only enabled because the default -march is armv7-a+fp. The kernel build
is overriding GCC's (new) built-in default march to one that does not
have "+fp",
I wonder if this is due to:
gcc-11 (11.1.0-2) experimental; urgency=medium
[...]
* For armhf configure --with-arch=+fp, dropping the --with-fpu= option.
[...]
FWIW, I'm seeing something similar w/ edk2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
23 matches
Mail list logo
