libtool: update to 2.4.7.

[oreo639]

Testing the changes

• I tested the changes in this PR: briefly

Most of the testing for this was done as a part of the gcc12 PR, this was split on request.

Most of the build failures experienced were due to hardcoded version-mismatches and the libtool files not getting regenerated properly.
This also defines lt_cv_shlibpath_overrides_runpath=yes on musl since it always searches LD_LIBRARY_PATH before RPATH and RUNPATH and not defining it causes some tests to fail which verify this behavior.

Please test this PR before merging.

[dkwo]

I wonder if this also fixes the failing ntl build on aarch64-musl #37497
I'll have a machine to test it in a few weeks.

[dkwo]

@paper42 Do you have a quick way of building ntl natively on aarch64-musl using this pr?

[dkwo]

Built and checked this PR for aarch64-musl.
It also fixes the previously reported ntl build failure #37497 @tornaria

[dkwo]

@oreo639 what is the status of this? can you rebase it?

[oreo639]

what is the status of this?

I temporarily marked it as a draft because wanted to make sure this didn't get merged with an outdated changeset.

[oreo639]

The libtool tests are failing due to the grep update.

[dkwo]

it seems there's yet another cross-compilation issue with libtool: if i use the packaged libtool to compile ntl, then it fails, as previously reported, while if i natively compile libtool first, then I can successfully use it to build ntl (on aarch64), including passing tests.

[oreo639]

I can't build natively on aarch64.
Build the packages with -C and try running a diff between them and let me know what the difference is.

[oreo639]

Oh I see:

# The directories searched by this compiler when creating a shared library.
compiler_lib_search_dirs="/usr/lib/gcc/aarch64-linux-gnu/10.2.1 /usr/lib/gcc/aarch64-linux-gnu/10.2.1/../../../../aarch64-linux-gnu/lib/../lib64 /usr/aarch64-linux-gnu/lib/../lib64 /usr/aarch64-linux-gnu/usr/lib/../lib64 /usr/lib/gcc/aarch64-linux-gnu/10.2.1/../../../../aarch64-linux-gnu/lib /usr/aarch64-linux-gnu/lib /usr/aarch64-linux-gnu/usr/lib"

# Dependencies to place before and after the objects being linked to
# create a shared library.
predep_objects="/usr/lib/gcc/aarch64-linux-gnu/10.2.1/../../../../aarch64-linux-gnu/lib/../lib64/crti.o /usr/lib/gcc/aarch64-linux-gnu/10.2.1/crtbeginS.o"
postdep_objects="/usr/lib/gcc/aarch64-linux-gnu/10.2.1/crtendS.o /usr/lib/gcc/aarch64-linux-gnu/10.2.1/../../../../aarch64-linux-gnu/lib/../lib64/crtn.o"
predeps=""
postdeps="-lstdc++ -lm -lgcc_s -lc -lgcc_s"

# The library search path used internally by the compiler when linking
# a shared library.
compiler_lib_search_path="-L/usr/lib/gcc/aarch64-linux-gnu/10.2.1 -L/usr/lib/gcc/aarch64-linux-gnu/10.2.1/../../../../aarch64-linux-gnu/lib/../lib64 -L/usr/aarch64-linux-gnu/lib/../lib64 -L/usr/aarch64-linux-gnu/usr/lib/../lib64 -L/usr/lib/gcc/aarch64-linux-gnu/10.2.1/../../../../aarch64-linux-gnu/lib -L/usr/aarch64-linux-gnu/lib -L/usr/aarch64-linux-gnu/usr/lib"

That's definitely not right.

The cross compiler paths are supposed to have gotten wiped out here:
https://github.com/oreo639/void-packages/blob/b255a33115e72d753a90432950c3864be983606e/srcpkgs/libtool/template#L44-L46
But since these are relative paths, they leaked through.