Page MenuHomeFreeBSD

arm: fail early on gcc builds
ClosedPublic

Authored by brooks on Tue, May 14, 12:11 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, May 22, 12:13 PM
Unknown Object (File)
Wed, May 22, 4:35 AM
Unknown Object (File)
Mon, May 20, 4:17 AM
Unknown Object (File)
Sat, May 18, 1:07 AM
Unknown Object (File)
Fri, May 17, 4:45 PM
Unknown Object (File)
Wed, May 15, 6:58 PM
Unknown Object (File)
Tue, May 14, 7:12 AM
Unknown Object (File)
Tue, May 14, 7:12 AM
Subscribers

Details

Summary

Since at least 2022 (see https://reviews.freebsd.org/D36754), it has
not been possible to build armv6/armv7 with gcc due to atomics macros
gcc doesn't like. Prevent developers doing due diligance from wasting
time and CPU cycles on this combination as it just fails to build in
libc.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

I'd be more inclined to land the other review, but until it does, this isn't bad.

This revision is now accepted and ready to land.Tue, May 14, 6:31 PM

I have a few fixes for some of the build issues with gcc, but c++ bits of world and kernel modules are broken.

Makefile.inc1
180

I've seen more issues than that with gcc 13

Only amd64 and i386 successfully build with GCC currently. risc-v needs GCC's libatomic to link, powerpc and arm break in various ways. There's a reason that only amd64 GCC builds are enabled in CI. The toolchains do exist for all of our platforms, but getting things to build there is more of an aspiration.

This revision was automatically updated to reflect the committed changes.