On Tue, 5 Aug 2025, John Ericson wrote:
> > That's unavoidable to some extent, given that the GCC libraries have
> > additional concepts for installation directories (such as a directory for
> > shared libgcc used at runtime separate from directories used at compile
> > time).
>
> What's the runtime one for? RPATH and friends?
I think RPATH should generally be discouraged, and slibdir (as configured
using --with-slibdir=) reflects configurations where e.g. shared libgcc
goes in /lib but shared libstdc++ and other libraries go in /usr/lib.
(Nowadays those tend to be the same directory on GNU/Linux systems.)
> OK so it sounds like a first step might be to find some other change we
> agree on, and build momentum from there.
>
> Maybe the top srcdir example above is a place to begin? I saw lots of
> raw "${srcdir}/.." in the libgcc build system, and by contrast
> `libgcc_topdir` is barely used. Some of the flag variables mentioned
> there only seems defined in select few projects, too. This makes me
> suspect most of those branches might be dead code.
>
> Let me know, and if so, I can make a new patch removing them. Maybe
> after a couple rounds of that we'll have "decluttered the workbench", so
> to speak.
I'm not sure source directory references have that much relevance to
cleaning up installation directory references, but I certainly expect
there's scope for such cleanup.
--
Joseph S. Myers
josmy...@redhat.com
