Bug 927650 – dev-libs/libgcrypt-1.10.3-r1 fails to compile during world re-emerge after updating to 23.0 profile

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Ben Buhse 2024-03-23 21:17:32 UTC]

I'm in the process of upgrading to amd64/23.0/split-usr/desktop from amd64/17.1/desktop and I'm currently at the final step, rebuilding world, but dev-libs/libgcrypt is failing because of this:

```
libtool: Version mismatch error.  This is libtool 2.4.2 Debian-2.4.2-1, but the
libtool: definition of this LT_INIT comes from libtool 2.4.7.
libtool: You should recreate aclocal.m4 with macros from libtool 2.4.2 Debian-2.4.2-1
libtool: and run autoconf again.
```

Reproducible: Always

Steps to Reproduce:
1. Follow the steps from the "Profile upgrade to version 23.0 available" portage news
2. emerge --ask --emptytree --getbinpkg @world
Actual Results:  
The emerge fails while trying to emerge dev-libs/libgcrypt-1.10.3-r1

Expected Results:  
The emerge continues until everything is re-emerged

emerge --info: https://bpa.st/G2EQ
emerge -pqv: https://bpa.st/HO3Q
build log: https://bpa.st/WCPA

Here ( https://bpa.st/CWPQ ) you can see I re-emerged binutils, gcc, glibc, and libtool in that order starting at Sat Mar 23 10:31:05 2024.

[Comment 1 Sam James 2024-03-23 21:19:55 UTC]

Please use attachments rather than pastebins, as they expire and may not be accessible via firewalls.

[Comment 2 Ben Buhse 2024-03-23 21:24:53 UTC]

Created attachment 888336 [details]
dev-libs/libgcrypt-1.10.3-r1 build.log

[Comment 3 Ben Buhse 2024-03-23 21:25:40 UTC]

Created attachment 888337 [details]
emerge -pqv '=dev-libs/libgcrypt-1.10.3-r1::gentoo'

[Comment 4 Ben Buhse 2024-03-23 21:26:13 UTC]

Created attachment 888338 [details]
emerge --info '=dev-libs/libgcrypt-1.10.3-r1::gentoo'

[Comment 5 Ben Buhse 2024-03-23 21:26:34 UTC]

(In reply to Sam James from comment #1)
> Please use attachments rather than pastebins, as they expire and may not be
> accessible via firewalls.

Sorry about that, I've added them as attachments now.

[Comment 6 Ben Buhse 2024-03-23 23:18:44 UTC]

Created attachment 888342 [details]
emerge --info libtool

Here's emerge --info for libtool, I *did* follow the step to emerge it before re-emerging world

[Comment 7 Ben Buhse 2024-03-24 01:03:55 UTC]

I also just realized that if I try to run libtool I get this

```
$ libtool
bash: /usr/bin/libtool: /usr/bin/bash: bad interpreter: No such file or directory
```

[Comment 8 Ben Buhse 2024-03-24 01:21:10 UTC]

(In reply to Ben from comment #7)
> I also just realized that if I try to run libtool I get this
> 
> ```
> $ libtool
> bash: /usr/bin/libtool: /usr/bin/bash: bad interpreter: No such file or
> directory
> ```

So it seems like this is something to do with the binpkg for libtool.

The shebang is `#! /usr/bin/bash` when I install the binpkg, but `#! /bin/bash` when I install it from source. When I install it from source, I'm able to build libgcrypt fine.

```
[gentoobinhost]
priority = 1
sync-uri = https://distfiles.gentoo.org/releases/amd64/binpackages/23.0/x86-64-v3 
```

This is my `gentoobinhost.conf` file after upgrading profiles. I used the `-v3` because I've got an AMD 7840U on this machine, so it should be supported.

[Comment 9 Ben Buhse 2024-03-24 01:23:04 UTC]

> This is my `gentoobinhost.conf` file after upgrading profiles. I used the
> `-v3` because I've got an AMD 7840U on this machine, so it should be
> supported.

Sorry for the spam, but I just checked and the same `/usr/bin/bash` shebang happens when using the regular x86-64 sync-uri as well.

[Comment 10 Sam James 2024-03-24 09:02:23 UTC]

Thanks. On it.

[Comment 11 Larry the Git Cow 2024-03-24 09:07:26 UTC]

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c7012f128a3c04053924fa1e96ed48a1c758fc65

commit c7012f128a3c04053924fa1e96ed48a1c758fc65
Author:     Sam James <[e-mail]>
AuthorDate: 2024-03-24 09:05:20 +0000
Commit:     Sam James <[e-mail]>
CommitDate: 2024-03-24 09:06:11 +0000

    dev-build/libtool: fix shebang for bash
    
    Always use ${EPREFIX}/bin/bash rather than the current path to bash, so that
    we work on both usr-merged and non-usr-merged systems.
    
    Bug: https://bugs.gentoo.org/927662
    Closes: https://bugs.gentoo.org/927650
    Signed-off-by: Sam James <[e-mail]>

 dev-build/libtool/{libtool-2.4.7-r2.ebuild => libtool-2.4.7-r3.ebuild} | 2 +-
 dev-build/libtool/libtool-9999.ebuild                                  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

[Comment 12 Larry the Git Cow 2024-03-24 09:09:31 UTC]

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=18f979e09388597a04255a2f42c464cf5a05d512

commit 18f979e09388597a04255a2f42c464cf5a05d512
Author:     Sam James <[e-mail]>
AuthorDate: 2024-03-24 09:08:48 +0000
Commit:     Sam James <[e-mail]>
CommitDate: 2024-03-24 09:08:48 +0000

    autotools.eclass: require >=dev-build/libtool-2.4.7-r3
    
    Needed for c7012f128a3c04053924fa1e96ed48a1c758fc65 wrt upgrade ordering.
    
    Bug: https://bugs.gentoo.org/927650
    Bug: https://bugs.gentoo.org/927662
    Signed-off-by: Sam James <[e-mail]>

 eclass/autotools.eclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

[Comment 13 Sam James 2024-03-24 09:26:20 UTC]

*** Bug 927662 has been marked as a duplicate of this bug. ***