[OpenIndiana-discuss] Problems with gcc-7 and gcc-10 built binaries
Stephan Althaus
Stephan.Althaus at Duedinghausen.eu
Mon May 22 12:37:15 UTC 2023
On 5/21/23 22:35, russell wrote:
> Hi
>
> Back in October 2022, when I was experiencing issues building
> libfilezilla in response to my posting Till pointed out that gcc-7 and
> gcc-10 have an ABI break.
>
> 7/10/22 18:22, Till Wegmueller wrote:
>
>> Hi Russel
>>
>> Thats an ABI break.
>>
>> Looks like Gcc7 and Gcc10 produce different output.
>>
>> You will have to compile all with the same compiler.
>>
>> -Till
>
>
> So, are there plans to switch to using gcc-10 for the entire build of
> OpenIndiana to eliminate the ABI compatibility issue of mixing gcc-7
> and gcc-10?
>
> Kind Regards
>
> Russell
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
Hello!
In oi-userland/make-rules/shared-macros.mk:GCC_VERSION = 10
is set, so the default compiler is 10.
The pkg binaries may be a little behind, as the packages must be rebuild
on the build server since that setting changed.
But i think there is a good chance that the packages are already build
with gcc-10,
you just have to update your system with "pkg update".
Regards,
Stephan
P.S. you could use 'ldd' to examine the linkage of a binary, be sure
that there is no gcc/7 path in the libs used, and the libs used by the
libs ... :-)
$ ldd `which firefox`
libpthread.so.1 => /lib/64/libpthread.so.1
libsocket.so.1 => /lib/64/libsocket.so.1
libstdc++.so.6 => /usr/gcc/10/lib/amd64/libstdc++.so.6
libm.so.2 => /lib/64/libm.so.2
librt.so.1 => /lib/64/librt.so.1
libgcc_s.so.1 => /usr/gcc/10/lib/amd64/libgcc_s.so.1
More information about the openindiana-discuss
mailing list