Date: Tue, 24 Sep 2024 11:08:36 +0000 From: Lorenzo Salvadore <developer@lorenzosalvadore.it> To: Alex Arslan <ararslan@comcast.net> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Wrong OSABI for GCC from Ports Message-ID: <cK0sQAOK_3qWKZKiqLN7DikBu2jB5J7ThVBvKg21MRSOWC8Nh0CoD8S-vplq4qNTqnWr-8PbhmEdFZV6Hck2Wuyf-5YqOxobutfS0x3s9WY=@lorenzosalvadore.it> In-Reply-To: <E3003E21-2D7B-4A13-8FE7-97EF5BE75D32@comcast.net> References: <E3003E21-2D7B-4A13-8FE7-97EF5BE75D32@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, September 10th, 2024 at 18:13, Alex Arslan <ararslan@comcast.net> wrote: > > > 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. Hello, 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=281681 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? Thanks for your bug report, Lorenzo Salvadore
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cK0sQAOK_3qWKZKiqLN7DikBu2jB5J7ThVBvKg21MRSOWC8Nh0CoD8S-vplq4qNTqnWr-8PbhmEdFZV6Hck2Wuyf-5YqOxobutfS0x3s9WY=>