Date: Tue, 24 Sep 2024 09:05:45 -0700 From: Alex Arslan <ararslan@comcast.net> To: Lorenzo Salvadore <developer@lorenzosalvadore.it> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Wrong OSABI for GCC from Ports Message-ID: <52727CFE-BE16-4778-83BD-2EE07B44C9A5@comcast.net> In-Reply-To: <cK0sQAOK_3qWKZKiqLN7DikBu2jB5J7ThVBvKg21MRSOWC8Nh0CoD8S-vplq4qNTqnWr-8PbhmEdFZV6Hck2Wuyf-5YqOxobutfS0x3s9WY=@lorenzosalvadore.it> References: <E3003E21-2D7B-4A13-8FE7-97EF5BE75D32@comcast.net> <cK0sQAOK_3qWKZKiqLN7DikBu2jB5J7ThVBvKg21MRSOWC8Nh0CoD8S-vplq4qNTqnWr-8PbhmEdFZV6Hck2Wuyf-5YqOxobutfS0x3s9WY=@lorenzosalvadore.it>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sep 24, 2024, at 4:08=E2=80=AFAM, Lorenzo Salvadore = <developer@lorenzosalvadore.it> wrote: >=20 > On Tuesday, September 10th, 2024 at 18:13, Alex Arslan = <ararslan@comcast.net> wrote: >=20 >>=20 >>=20 >> I noticed that GCC and its associated libraries, when installed from = pkg >> on FreeBSD 14.1 AArch64, have an OS/ABI value of NONE (0) rather than >> FreeBSD (9), as reported by readelf --file-header. I also observed = this >> when cross compiling GCC for FreeBSD 13.2 AArch64 on Alpine Linux; I >> assumed it was an issue with the cross compilation setup until I = realized >> that the one from pkg exhibited the same thing. This does not seem to >> occur with x86_64, neither from pkg nor cross compiled. Does anyone = know >> why this would happen and whether it could be addressed with a patch = to >> GCC? Apologies if this is already known and has been discussed = somewhere. >=20 > Hello, >=20 > I am the maintainer for the GCC ports, sorry for the late response. > I have created a bug report to track this issue, so we do not forget > about it: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281681 Thank you! Mik=C3=A4el Urankar pointed out that what I described sounds = similar to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252490 and I = believe it is actually the exact same phenomenon as what I described. > Is the bug only about the value reported by readelf? Or is the = compiler > actually broken? If the compiler works, what is the value reported by > readelf for binary compiled by it? The compiler itself works just fine, it's only the OS/ABI in the ELF = file header that isn't set to FreeBSD. It does have a FreeBSD branded ELF = note though. Binaries produced by cc set OS/ABI to FreeBSD and include the = ELF note, whereas binaries produced by the GCC port (13.2.0) have OS/ABI set to NONE but do still include the branded ELF note. The produced binaries are similarly functional. Based on the discussion in Mik=C3=A4el's bug report, it sounds like this behavior is expected, so I guess there's no bug after all? > Thanks for your bug report, >=20 > Lorenzo Salvadore >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52727CFE-BE16-4778-83BD-2EE07B44C9A5>