|Summary:||Clean up some autotools warnings|
|Product:||WebKit||Reporter:||Daniel Macks <firstname.lastname@example.org>|
|Component:||New Bugs||Assignee:||Nobody <email@example.com>|
|Version:||528+ (Nightly build)|
|OS:||Mac OS X 10.4|
Building r39007 on OS X 10.4 with autoconf-2.63 automake-1.10.2 libtool-2.2.4, autogen.sh whines: libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. So okay, let's do that.
Created an attachment (id=25820) [details] Add autotools flags as requested by current autotools versions With this patch, autogen gives: >libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. >libtoolize: linking file `m4/libtool.m4' >libtoolize: linking file `m4/ltoptions.m4' >libtoolize: linking file `m4/ltsugar.m4' >libtoolize: linking file `m4/ltversion.m4' >libtoolize: linking file `m4/lt~obsolete.m4' >libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. Looks like libtool is doing a simple grep in Makefile.am, doesn't know WebKit uses GNUmakefile.am instead. Why *does* it use GNUmakefile instead of Makefile?
(In reply to comment #1) > Looks like libtool is doing a simple grep in Makefile.am, doesn't know WebKit > uses GNUmakefile.am instead. Why *does* it use GNUmakefile instead of Makefile? Because Makefile is used for other purposes.
(From update of attachment 25820 [details]) r=me tabs in ChangeLog
Could you please set a valid email address in future patches?
Yes, autotools complains about not adding m4. But this directory does not even exist and is breaking the build for others... I will back this patch out and we can look for another solution.
(From update of attachment 25820 [details]) Clearing review flag since it appears that this patch was rolled out.
Experimenting further, this patch (nor any similar variant I tried) doesn't fully clear the warnings reliably. I talked to a libtool developer who said they only recently became aware of gnumakefile.am as an alternative to makefile.am. I'm (now) not surprised that there are warnings and that trying to fix them creates other problems at this time:(