Bluz You Should Recreate Aclocalm4 With Aclocal and Run Automake Again

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

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

UlFie

Pita · Tux'due south lil' helper Joined: 09 April 2020 Posts: 101

Information technology fails on the make. Hither'due south the full output:

UlFie

It'south never a good thought 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: Midweek May 20, 2020 7:l pm Post subject:

Y'all could try looking at the output of observe . -proper name '*.m4' -exec grep -E 'macro_(version|revision)' {} +, in the aforementioned directory you were running those commands, and see if there's anything resembling a version number that is non ii.iv.6.

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

Pita · Tux'south lil' helper Joined: 09 April 2020 Posts: 101

GDH-gentoo · Posted: Wednesday May xx, 2020 9:25 pm Post discipline:

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

? Fine, try grep -E 'macro_(version|revision)' m4/* and encounter if there's anything resembling a version number that is non ii.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 April 2020 Posts: 101

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

Are you irresolute things betwixt each mail and not telling? That looks OK, postal service now the output of grep -Due east '(macro_version|_revision|VERSION=)' libtool in the same directory yous ran the original commands.

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

I oasis't changed anything

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

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

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

UlFie · Posted: Thu May 21, 2020 two:52 pm Mail subject:

GDH-gentoo · Posted: Thu May 21, 2020 3:05 pm Mail service subject area:

Whatsoever the crusade is, something is not working well with the build system. The libtool script is generated by the configure script, which is generated in plough 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 April 2020 Posts: 101

What boosted data practice you need to help diagnose this? I'll mail whatever yous need

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

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

Pita · Tux'due south 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 April 2020 Posts: 101

GDH-gentoo · Posted: Thu May 21, 2020 6:14 pm Post field of study:

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

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

thammer · n00b Joined: 14 May 2020 Posts: fifteen

After dealing with a few other items in this upgrade saga, I am dorsum to this issue. As a summary, at this step nosotros are building some PHP extension code and have experienced a failure due to "macro_revision" not being divers in the generated libtool script.
My biggest frustration is that this occurs randomly in the pre-upgrade surround (if I just run the build multiple times, it will eventually succeed). When nosotros first encountered it during this upgrade procedure 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 inside the chroot jail from here on.

Later a hint in another libtool issue thread, I realized that the ltmain.sh in /usr/lib/php7.4/lib/build/ was VERSION=1.five.6. Later on 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 sally is using).
Still thinking it might be related, I copied the 2.four.6 ltmain.sh file from /usr/share/libtool/build-aux/ to /usr/lib/php7.4/lib/build/ but information technology made no difference.
And 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 still to locate it. The phpize pace creates the build/ directory with (most of?) the m4 files and some others including ltmain.sh which shows VERSION=ii.4.vi.

The aclocal step still shows the warning:

Bluz You Should Recreate Aclocalm4 With Aclocal and Run Automake Again

0 Response to "Bluz You Should Recreate Aclocalm4 With Aclocal and Run Automake Again"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel