URL:
<http://savannah.gnu.org/support/?108503>
Summary: Running autoscan in a directory with ltmain.sh
produces conflicting warnings with libtoolize about AC_PROG_RANLIB
Project: Autoconf
Submitted by: egallager
Submitted on: Thu 13 Feb 2014 12:58:01 AM GMT
Category: None
Priority: 5 - Normal
Severity: 2 - Minor
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Operating System: Mac OS
_______________________________________________________
Details:
Let's say that, in an empty directory, I have a configure.ac file that looks
like this:
AC_INIT([testcase])
LT_INIT
AC_OUTPUT
Then I autoreconf, which puts ltmain.sh into the current directory. Now when I
run autoscan, it produces the following warnings:
Local-Admins-MacBook-Pro:autoconf_bug_reports_dir localadmin$ autoscan
configure.ac: warning: missing AC_PROG_CXX wanted by: ltmain.sh:960
configure.ac: warning: missing AC_PROG_INSTALL wanted by: ltmain.sh:1028
configure.ac: warning: missing AC_PROG_MAKE_SET wanted by: ltmain.sh:2163
configure.ac: warning: missing AC_PROG_RANLIB wanted by: ltmain.sh:2455
So I add these macros to my configure.ac, and now, when I autoreconf again, it
includes this warning:
glibtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT'
If I then go and remove AC_PROG_RANLIB, autoscan will then warn about it being
missing again the next time I run it, leading to an endless cycle of
conflicting warnings. Perhaps autoscan could be modified to just ignore
ltmain.sh when scanning?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/support/?108503>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
