On Wed, 29 May 2024 10:33:16 +0100
Jonathan Wakely wrote:
> > 1. Some GCC binaries hardcode RUNPATH and use
>
> Binaries, or just libraries?
>
I meant GCC shared library binaries. The actual executables under bin/
do not use RUNPATH with GCC default build behaviour.
I think FreeBSD GCC compil
On Wed, 29 May 2024 at 09:15, Sad Clouds via Gcc wrote:
>
> On Wed, 29 May 2024 09:05:50 +0200
> Richard Biener wrote:
>
> > If you build an executable to pick up libstdc++ via a RUNPATH that apps
> > RUNPATH
> > should apply to libgcc as well. If you use LD_LIBRARY_PATH the story
> > is the sa
On Wed, May 29, 2024 at 10:14 AM Sad Clouds wrote:
>
> On Wed, 29 May 2024 09:05:50 +0200
> Richard Biener wrote:
>
> > If you build an executable to pick up libstdc++ via a RUNPATH that apps
> > RUNPATH
> > should apply to libgcc as well. If you use LD_LIBRARY_PATH the story
> > is the same.
>
On Wed, 29 May 2024 09:05:50 +0200
Richard Biener wrote:
> If you build an executable to pick up libstdc++ via a RUNPATH that apps
> RUNPATH
> should apply to libgcc as well. If you use LD_LIBRARY_PATH the story
> is the same.
>
> So what's your actual failure mode?
Hello, the concern I have
On Wed, May 29, 2024 at 8:47 AM Sad Clouds via Gcc wrote:
>
> Hello, I'm noticing some issues with libstdc++ after building GCC from
> sources and installing into /opt/gcc-14.1.0. Specifically:
>
> $ objdump -x /opt/gcc-14.1.0/lib/libstdc++.so.6 | grep RUNPATH
>
> $ ldd /opt/gcc-14.1.0/lib/libstdc
Hello, I'm noticing some issues with libstdc++ after building GCC from
sources and installing into /opt/gcc-14.1.0. Specifically:
$ objdump -x /opt/gcc-14.1.0/lib/libstdc++.so.6 | grep RUNPATH
$ ldd /opt/gcc-14.1.0/lib/libstdc++.so.6
/opt/gcc-14.1.0/lib/libstdc++.so.6:
libm.so.5 => /lib/l
