FS#33246 - [automake] aclocal fails to run for curl

Attached to Project: Arch Linux
Opened by Dave Reisner (falconindy) - Sunday, 30 December 2012, 15:21 GMT
Last edited by Dave Reisner (falconindy) - Monday, 14 January 2013, 03:37 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Leaving this here because I'm not sure if it's curl at fault or automake 1.13 (but I suspect the latter). Running curl's buildconf (aka autogen.sh) bombs when it runs aclocal, with 2 independent errors:

buildconf: autoconf version 2.69 (ok)
buildconf: autom4te version 2.69 (ok)
buildconf: autoheader version 2.69 (ok)
buildconf: automake version 1.13 (ok)
buildconf: aclocal version 1.13 (ok)
buildconf: libtool version 2.4.2 (ok)
buildconf: GNU m4 version 1.4.16 (ok)
buildconf: running libtoolize
buildconf: converting all mv to mv -f in local m4/libtool.m4
buildconf: running aclocal
Use of uninitialized value $item in exists at /usr/share/automake-1.13/Automake/General.pm line 60, <GEN131> line 824.
Use of uninitialized value $item in hash element at /usr/share/automake-1.13/Automake/General.pm line 62, <GEN131> line 824.
Use of uninitialized value $m4dir in opendir at /usr/bin/aclocal line 368.
Use of uninitialized value $m4dir in concatenation (.) or string at /usr/bin/aclocal line 372.
aclocal: error: couldn't open directory '': No such file or directory
buildconf: aclocal command failed
This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 14 January 2013, 03:37 GMT
Reason for closing:  Fixed
Comment by Dave Reisner (falconindy) - Sunday, 30 December 2012, 23:42 GMT
Narrowed this down to curl-override.m4 in the m4/ subdir of curl. They actually override an automake macro, which causes the bizzare behavior... uggh.
Comment by Dave Reisner (falconindy) - Monday, 14 January 2013, 03:37 GMT

Loading...