[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New libtool maintainer: request for feedback

From: Alex Ameen
Subject: Re: New libtool maintainer: request for feedback
Date: Tue, 26 Oct 2021 21:11:08 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0

Thanks for the heads up.

I will take a look at this as soon as I can. I'm still working my way through a lot of the boilerplate new maintainer stuff, which at least for `libtool' is a lot to unpack ( but I'm making good progress ).

From the sounds of it `libtoolize' seems to have several conflicts with the rest of `autotools' that need to get ironed out. Could you provide info about tool versions and relevant `'/`' snippets? I'll start by adding a test case for it.

The need for `ACLOCAL_AMFLAGS' always seemed wonky to me as well; I'll look at getting it removed. Off the top of my head I imagine `autom4te -l autoconf -t AC_CONFIG_MACRO_DIRS:\$%;' somewhere in `libtoolize' would do the trick ( we'll hope it's that easy at least haha ).

On 10/26/21 11:16 AM, Marko Lindqvist wrote:
  Sorry if this is actually covered by more-to-detail suggestions, but
I don't know the internal details of autotools well enough to tell if
it is.

  As a maintainer of a autotools using project, I've been waiting for a
release that resolves issues with removal of ACLOCAL_AMFLAGS. With
newer automake it's supposedly not needed, but I think it's libtoolize
that spits out various warnings (" warning: macro
'AM_LANGINFO_CODESET' not found in library", and in some environments
even right out suggestion to *add* ACLOCAL_AMFLAGS) when it's removed.

  - ML

reply via email to

[Prev in Thread] Current Thread [Next in Thread]