Re: cwrapper g++ -v erroring out (Re: Help with attempt to update devel/gdb (currently in wip/gdb))

["Dr. Thomas Orgis" <thomas.orgis%uni-hamburg.de@localhost>]

Am Sat, 26 Apr 2025 08:57:50 +0200
schrieb "Dr. Thomas Orgis" <thomas.orgis%uni-hamburg.de@localhost>:

> But that doesn't work when the build does further configery in the make
> stage:-(  Gdb contains sub-projects, and for some reason it's organized
> to run the sub-configures on build after the main configure. Maybe we
> could pre-empt that, but it's annoying.

If you do

	make configure-gdb

it does not just run configure scripts, it builds dependencies. The
included gnulib, libiberty, readline (without --with-system-readline) …
before configuring gdb. We'd need to disentangle the whole vendoring in
this builds-within-build. Now you could say this is bad practice, but
in the world of rust and go, I don't see how we could prohibit
vendoring for autotools projects … and then even such basic and complex
ones like the debugger, which may have its reasons to use specific
copies of libraries.

So I'm back and wondering if we really need to replace the libtools.
What is the motivation for the wrapper there? If we are serious about
libtool replacements, this must be done before configure, by hacking
the respective generator scripts (ltmain.sh, libtool.m4?).


Alrighty then,

Thomas

-- 
Dr. Thomas Orgis
HPC @ Universität Hamburg