tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

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



Am Sat, 26 Apr 2025 00:34:14 +0200
schrieb Jörg Sonnenberger <joerg%bec.de@localhost>:

> > 1. bmake build-env, in there
> > 2. make new work directory, call ../gdb-16.2/configure
> > 3. mkdir gdb; ../../gdb-16.2/gdb/configure; cd ..
> > 4. mkdir gdb-no-cwrapper; PATH=$(drop_cwrapper_path $PATH) ../../gdb-16.2/gdb/configure;  cd ..
> > 
> > The difference in the two generated gdb/libtool files is apparent:  
> 
> The generated libtool shouldn't be used though.

OK, so we got two issues:

1. The generated libtool in gdb subproject directories is bad due to
cwrapper changing compiler behaviour von `cc -v` (see other mails).
That should be fixed regardless, or not?

2. That generated libtool is actually used.

As to the procedure above, the libtool generation happends in a
second-stage configure invocation.


cd build
../gdb-16.2/configure …
make ← gdb/libtool is generated here!

Pkgsrc replaces libtool by

#!/bin/bash
exec /nfs/ssd2.2/u/sw/work/a770de/pkgsrc/2025Q1-devel/bw/audio/mpg123/work/.cwrapper/bin/libtool "$@"

between configure and make stages, indicated by

=> Modifying libtool scripts to use pkgsrc libtool
=> Modifying libtool scripts to use pkgsrc depcomp

(Interesting, not /bin/sh ? Could save some milliseconds there on invocation on Debian! ;-)

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.

What purpose has the cwrapped libtool, actually? What is broken when
the generated libtool is used (and works), like it is now for wip/gdb?

Suggestions on how to best handle this? Maybe there's a (list of)
target to invoke post-configure to get the subordinate configure runs,
then one can replace libtools?


Alrighty then,

Thomas

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


Home | Main Index | Thread Index | Old Index