GNU bug report logs - #73620
libtool-2.5.3 broken on CentOS and Alma Linux

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#73620: closed (libtool-2.5.3 broken on CentOS and Alma Linux)
Date: Thu, 10 Oct 2024 14:41:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Thu, 10 Oct 2024 17:39:15 +0300
with message-id <49e196e8-feec-44d0-8120-481abb37b7e4 <at> gmail.com>
and subject line Re: bug#73620: libtool-2.5.3 broken on CentOS and Alma Linux
has caused the debbugs.gnu.org bug report #73620,
regarding libtool-2.5.3 broken on CentOS and Alma Linux
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
73620: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=73620
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Bruno Haible <bruno <at> clisp.org>
To: bug-libtool <at> gnu.org
Subject: libtool-2.5.3 broken on CentOS and Alma Linux
Date: Fri, 04 Oct 2024 01:00:09 +0200

[Message part 3 (text/plain, inline)]

Hi,

In GNU gettext's CI, two months ago, I started using libtool-2.5.1.
All fine on all platforms.

This week, I upgraded to libtool-2.5.3, and what I see is that most
unit tests fail on CentOS 7 and Alma Linux 9, i.e. both RHEL compatible
distros.

How to reproduce:
0. Use a machine with Alma Linux 9 (e.g. from AlmaLinux-9.0-x86_64-dvd.iso
   with VirtualBox or QEMU).
1. Download the tarball generated by the CI:
  $ wget https://alpha.gnu.org/gnu/gettext/gettext-2024-10-02.tar.gz
2. Unpack
  $ tar xfz gettext-2024-10-02.tar.gz
3. Build
  $ mkdir build-64
  $ cd build-64
  $ ../configure
  $ make
  $ make check

Apparently the wrapper executables for most programs in gettext-tools/src/
are dysfunctional.

When I try to run one, in particular:
  $ cd gettext-tools/src
  $ ./xgettext --help
  /home/bruno/gettext-2024-10-02/build-64/gettext-tools/src/.libs/lt-xgettext: error while loading shared libraries: libtextstyle.so.0: cannot open shared object file: No such file or directory

But libtextstyle.so.0 exists in the build tree, at
  /home/bruno/gettext-2024-10-02/build-64/libtextstyle/lib/.libs/libtextstyle.so.0

I'm attaching the xgettext wrapper scripts
  - from Ubuntu 22.04 (where it works)
  - from Alma Linux 9 (where it is broken)

You can see that the main difference is that on Alma Linux, a relink command is
being used. This raises two questions:

  1) Why is the relink command not working? (Recall that omitting the relink
     is just an optimization.)

  2) Why is the "omit the relink" optimization not activated?

Bruno

[ubuntu-xgettext-wrapper (application/x-shellscript, attachment)]

[alma9-xgettext-wrapper (application/x-shellscript, attachment)]

[Message part 6 (message/rfc822, inline)]

From: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
To: 73620-done <at> debbugs.gnu.org
Cc: Sergey Poznyakoff <gray <at> gnu.org.ua>, Bruno Haible <bruno <at> clisp.org>,
 Sam James <sam <at> gentoo.org>
Subject: Re: bug#73620: libtool-2.5.3 broken on CentOS and Alma Linux
Date: Thu, 10 Oct 2024 17:39:15 +0300

[Message part 7 (text/plain, inline)]

On 10/10/2024 00:04, Bruno Haible wrote:
> Sergey Poznyakoff wrote:
>> Ileana is absolutely right: the reason for this behavior is that some
>> paths are excluded from compile_rpath in func_mode_link.  The original
>> idea was to prevent paths from outside of the source tree from appearing
>> before ones lying beneath it.  However, simply omitting such paths was
>> not right, they should be reordered instead.  The attached patch fixes
>> this.  With it, both bug_71489.at in libtool, and all tests in gettext
>> pass.
>

I am glad I understood correctly, and thank you for the patch!

> Thanks. I confirm that with this patch, all gettext tests pass. The xgettext
> wrapper script (attached) now has the complete relink command:
> 
> with libtool-2.5.3:
> relink_command="(... -Wl,-rpath -Wl,/home/bruno/inst-x86_64-64/lib)"
> with your new patch added:
> relink_command="(... -Wl,-rpath -Wl,/home/bruno/gettext-2024-10-02/build-64/libtextstyle/lib/.libs -Wl,-rpath -Wl,/home/bruno/inst-x86_64-64/lib)"
> 
> Ileana Dumitrescu wrote:
>> The relink command seems to be set by fast_install=yes:
> 
> Indeed, there is a difference here.
> 
> On Ubuntu 22.04:
> 
> $ grep fast_install ./gettext-runtime/libasprintf/config.status ./gettext-runtime/intl/config.status ./gettext-runtime/config.status ./libtextstyle/config.status ./gettext-tools/config.status
> ./gettext-runtime/libasprintf/config.status:enable_fast_install='needless'
> ./gettext-runtime/libasprintf/config.status:fast_install=$enable_fast_install
> ./gettext-runtime/intl/config.status:enable_fast_install='needless'
> ./gettext-runtime/intl/config.status:fast_install=$enable_fast_install
> ./gettext-runtime/config.status:enable_fast_install='needless'
> ./gettext-runtime/config.status:fast_install=$enable_fast_install
> ./libtextstyle/config.status:enable_fast_install='needless'
> ./libtextstyle/config.status:fast_install=$enable_fast_install
> ./gettext-tools/config.status:enable_fast_install='needless'
> ./gettext-tools/config.status:fast_install=$enable_fast_install
> 
> On Alma Linux 9:
> 
> $ grep fast_install ./gettext-runtime/libasprintf/config.status ./gettext-runtime/intl/config.status ./gettext-runtime/config.status ./libtextstyle/config.status ./gettext-tools/config.status
> ./gettext-runtime/libasprintf/config.status:enable_fast_install='yes'
> ./gettext-runtime/libasprintf/config.status:fast_install=$enable_fast_install
> ./gettext-runtime/intl/config.status:enable_fast_install='yes'
> ./gettext-runtime/intl/config.status:fast_install=$enable_fast_install
> ./gettext-runtime/config.status:enable_fast_install='yes'
> ./gettext-runtime/config.status:fast_install=$enable_fast_install
> ./libtextstyle/config.status:enable_fast_install='yes'
> ./libtextstyle/config.status:fast_install=$enable_fast_install
> ./gettext-tools/config.status:enable_fast_install='yes'
> ./gettext-tools/config.status:fast_install=$enable_fast_install
> 
> Where does this difference come from?
> hardcode_action is 'immediate' in both cases.
> inherit_rpath is 'no' in both cases.
> shlibpath_overrides_runpath is 'yes' on Ubuntu, 'no' on Alma Linux.
> Apparently the difference comes from the configure test marked with a comment
> "Some binutils ld are patched to set DT_RUNPATH"
> 
> Bruno
> 

Thank you for explaining how this works and differs between Ubuntu and 
Alma Linux. :)

I have applied the patch to the development branch [1], and I plan to
make another stable release soon for this and some other patches I have
not applied yet.

[1] 
https://git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=44ad06b0d260d4a6ac0f90834d505e1ee0077d53

-- 
Ileana Dumitrescu

GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354

[OpenPGP_0x6570EA01146F7354.asc (application/pgp-keys, attachment)]

[OpenPGP_signature.asc (application/pgp-signature, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.