Stuart Henderson <s...@spacehopper.org> writes:
> On 2021/02/23 17:17, Rafael Ávila de Espíndola wrote:
>>
>> Stuart Henderson <s...@spacehopper.org> writes:
>>
>> > On 2021/02/23 15:25, Stuart Henderson wrote:
>> >> I'll do some testing, I'm using this updated diff
>> >
>> > Oh yuk, gnu m4 is now needed at runtime for libtoolize.
>> > Is there a way around that?
>>
>> This is probably from
>>
>> - GNU M4 is required to run libtoolize in a directory with a
>> 'configure.ac' (or 'configure.in') that needs tracing to determine
>> what modes and directories have been specified.
>>
>> But unfortunately I have no idea how to avoid it, sorry. Maybe
>> libtoolize could be on its own sub package and only that depends on m4?
>
> A subpackage for libtoolize makes no sense. libtoolize and the libtool.m4
> files are literally all that are used by most ports using devel/libtool.
> Perhaps it can be persuaded to run with /usr/bin/m4 though, it depends
> what it wants from gm4.
Scrap that then. It is the first time I hear about libtoolize and the
manual page made me think it was something that was run once when
starting a project that uses libtool:
DESCRIPTION
Prepare a package to use libtool.
> Another problem showed up in the build,
>
> -----
> configure.in:16: error: Autoconf version 2.62 or higher is required
>
> /usr/local/share/aclocal/libtool.m4:96: LT_INIT is expanded from...
> /usr/local/share/aclocal/libtool.m4:100: AM_PROG_LIBTOOL is expanded from...
>
> configure.in:16: the top level
>
> autom4te-2.61: /usr/bin/m4 failed with exit status: 63
> aclocal-1.9: autom4te failed with exit status: 63
> -----
>
> With this update everything that uses both devel/libtool and autoconf
> needs to use autoconf >= 2.62.
>
> $ grep devel/libtool /usr/local/share/ports-INDEX | grep autoconf | grep -v
> 'autoconf/2\.6[2-9]' | cut -d'|' -f2
Interesting, so a project can depend on the gnu libtool both by depending
on devel/libtool or adding "USE_LIBTOOL = gnu"? I missed the first ones :-(
> audio/faad
> audio/fluidsynth
> audio/mp3blaster
> audio/swh-plugins
> audio/timidity
> audio/timidity,gtk2
> audio/timidity,xaw
> devel/ois
> emulators/x48
> games/numptyphysics
> games/numptyphysics,-npcomplete
> games/zangband
> games/zangband,no_x11
> graphics/agg
> graphics/geeqie
> misc/hfsplus
> net/ices2
> sysutils/colortail
> sysutils/inotify-tools
And given that it is better to just use the autoconf upstream uses, this
basically means waiting for these packages to change. Any idea how linux
distros handle this? I see, for example, that debian has many autoconf
versions, but only one version of libtool.
Cheers,
Rafael
