Libtool Version Mismatch issue

Pita · Tux's lil' helper Joined: 09 Apr 2020 Posts: 101

I've been trying to make a php ext for our project described here: https://forums.gentoo.org/viewtopic-t-1113056.html and I'm running into a version mismatch error for libtool. When I run make on my ext, I get this error:

UlFie

Pita · Tux's lil' helper Joined: 09 Apr 2020 Posts: 101

It fails on the make. Here's the full output:

UlFie · Posted: Wed May 20, 2020 5:30 pm Post subject:

It's never a good idea to ignore early warnings ;-)

.

Pita · Tux's lil' helper Joined: 09 Apr 2020 Posts: 101

I've fixed them all and I still get the same error

GDH-gentoo · Posted: Wed May 20, 2020 7:50 pm Post subject:

You could try looking at the output of find . -name '*.m4' -exec grep -E 'macro_(version|revision)' {} +, in the same directory you were running those commands, and see if there's anything resembling a version number that is not 2.4.6.

Also, I believe it is generally recommended to use the autoreconf command with suitable options instead of individually calling aclocal, autoheader, libtoolize and autoconf. See info autoreconf.

Pita · Tux's lil' helper Joined: 09 Apr 2020 Posts: 101

GDH-gentoo · Posted: Wed May 20, 2020 9:25 pm Post subject:

find finds .m4 files but grep says that they do not exist

? Fine, try grep -E 'macro_(version|revision)' m4/* and see if there's anything resembling a version number that is not 2.4.6. Is m4/ the only directory that contains .m4 files?

UlFie · Posted: Wed May 20, 2020 11:47 pm Post subject:

Pita · Tux's lil' helper Joined: 09 Apr 2020 Posts: 101

GDH-gentoo · Posted: Thu May 21, 2020 12:58 pm Post subject:

Are you changing things between each post and not telling? That looks OK, post now the output of grep -E '(macro_version|_revision|VERSION=)' libtool in the same directory you ran the original commands.

Pita · Tux's lil' helper Joined: 09 Apr 2020 Posts: 101

I haven't changed anything

GDH-gentoo · Posted: Thu May 21, 2020 1:48 pm Post subject:

OK, now post the output of phpize --clean && phpize && autoreconf --force --install --verbose --symlink && ./configure --enable-tsync, and then redo the previous grep command.

Pita · Tux's lil' helper Joined: 09 Apr 2020 Posts: 101

UlFie · Posted: Thu May 21, 2020 2:52 pm Post subject:

GDH-gentoo · Posted: Thu May 21, 2020 3:05 pm Post subject:

Whatever the cause is, something is not working well with the build system. The libtool script is generated by the configure script, which is generated in turn from other components. This is what the output of grep for a generated libtool script should look like:

Pita · Tux's lil' helper Joined: 09 Apr 2020 Posts: 101

What additional information do you need to help diagnose this? I'll post whatever you need

GDH-gentoo · Posted: Thu May 21, 2020 4:31 pm Post subject:

You didn't post the requested output. This would provide better information about what the build system is doing before starting to compile.

Pita · Tux's lil' helper Joined: 09 Apr 2020 Posts: 101

GDH-gentoo · Posted: Thu May 21, 2020 5:28 pm Post subject:

Pita · Tux's lil' helper Joined: 09 Apr 2020 Posts: 101

GDH-gentoo · Posted: Thu May 21, 2020 6:14 pm Post subject:

UlFie · Posted: Thu May 21, 2020 6:58 pm Post subject:

GDH-gentoo · Posted: Thu May 21, 2020 7:16 pm Post subject:

thammer · n00b Joined: 14 May 2020 Posts: 15

After dealing with a few other items in this upgrade saga, I am back to this issue. As a summary, at this step we are building some PHP extension code and have experienced a failure due to "macro_revision" not being defined in the generated libtool script.
My biggest frustration is that this occurs randomly in the pre-upgrade environment (if I just run the build multiple times, it will eventually succeed). When we first encountered it during this upgrade process it was happening every time. One person found that by deleting a backup file ({something}~) in the directory it started working.
I have since "started" over with the upgrade process and now seem to be back to it happening every time I try to build.

As you all have gleaned, the build is done in a chroot jail (and unfortunately some of the previous posts jumped back and forth between the host and the chroot environments). I will make all references and commands from within the chroot jail from here on.

After a hint in another libtool issue thread, I realized that the ltmain.sh in /usr/lib/php7.4/lib/build/ was VERSION=1.5.6. After resolving that other issue, I re-emerged dev-lang/php thinking it would resolve this issue. However, that file still is 1.5.6. (and I confirmed that it is actually coming from the php-7.4.6 tarball that emerge is using).
Still thinking it might be related, I copied the 2.4.6 ltmain.sh file from /usr/share/libtool/build-aux/ to /usr/lib/php7.4/lib/build/ but it made no difference.
So, I am back to still trying to figure this out the hard way...

I am stepping through the individual commands in build line that was originally posted trying to determine where things go awry, but have yet to locate it. The phpize step creates the build/ directory with (most of?) the m4 files and some others including ltmain.sh which shows VERSION=2.4.6.

The aclocal step still shows the warning: