MESSAGE
DATE | 2021-10-26 |
FROM | Alex Ameen
|
SUBJECT | Re: [Hangout - NYLXS] New libtool maintainer: request for feedback
|
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 `configure.ac'/`Makefile.am' 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 configure.ac -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 ("configure.ac:583: 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 _______________________________________________ Hangout mailing list Hangout-at-nylxs.com http://lists.mrbrklyn.com/mailman/listinfo/hangout
|
|