`autoreconf -i' from the the source tarball generates broken Makefile
---------------------------------------------------------------------

                 Key: TS-812
                 URL: https://issues.apache.org/jira/browse/TS-812
             Project: Traffic Server
          Issue Type: Bug
          Components: Build, Packaging
    Affects Versions: 2.1.9
         Environment: libtool 2.4, autoconf  2.68
            Reporter: Arno Toell
            Priority: Minor
             Fix For: 3.0.0


When running '_autoreconf -i_' from the release tarball (trunk is not affected) 
some/any of the generated Makefile templates being regenerated are 
syntactically broken. The results becomes visible when trying to compile ATS, 
in particular Allocator.cc. 

{code}
Making all in ts
make[3]: Entering directory 
`/home/arno/build-area/trafficserver-2.1.9-unstable/lib/ts'
(CDPATH="${ZSH_VERSION+.}:" && cd ../.. && /bin/bash 
/home/arno/build-area/trafficserver-2.1.9-unstable/build/aux/missing --run 
autoheader)
configure.ac:465: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from...
build/libtool.m4:1084: _LT_SYS_MODULE_PATH_AIX is expanded from...
build/libtool.m4:4211: _LT_LINKER_SHLIBS is expanded from...
build/libtool.m4:5343: _LT_LANG_C_CONFIG is expanded from...
build/libtool.m4:143: _LT_SETUP is expanded from...
build/libtool.m4:69: LT_INIT is expanded from...
build/libtool.m4:107: AC_PROG_LIBTOOL is expanded from...
configure.ac:465: the top level
configure.ac:465: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from...
build/libtool.m4:4211: _LT_LINKER_SHLIBS is expanded from...
build/libtool.m4:5343: _LT_LANG_C_CONFIG is expanded from...
build/libtool.m4:143: _LT_SETUP is expanded from...
build/libtool.m4:69: LT_INIT is expanded from...
build/libtool.m4:107: AC_PROG_LIBTOOL is expanded from...
configure.ac:465: the top level
configure.ac:465: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2662: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2679: AC_LINK_IFELSE is expanded from...
build/libtool.m4:1084: _LT_SYS_MODULE_PATH_AIX is expanded from...
build/libtool.m4:5428: _LT_LANG_CXX_CONFIG is expanded from...
build/libtool.m4:816: _LT_LANG is expanded from...
build/libtool.m4:799: LT_LANG is expanded from...
build/libtool.m4:827: _LT_LANG_DEFAULT_CONFIG is expanded from...
build/libtool.m4:143: _LT_SETUP is expanded from...
build/libtool.m4:69: LT_INIT is expanded from...
build/libtool.m4:107: AC_PROG_LIBTOOL is expanded from...
configure.ac:465: the top level
rm -f stamp-h1
touch ink_autoconf.h.in
cd ../.. && /bin/bash ./config.status lib/ts/ink_autoconf.h
config.status: creating lib/ts/ink_autoconf.h
config.status: lib/ts/ink_autoconf.h is unchanged
make  all-am
make[4]: Entering directory 
`/home/arno/build-area/trafficserver-2.1.9-unstable/lib/ts'
/bin/bash ../../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.   
-D_LARGEFILE64_SOURCE=1 -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT 
-Dlinux -I/usr/include/tcl8.4  -g -O2 -pipe -Wall -Werror -O3 
-feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -MT 
Allocator.lo -MD -MP -MF .deps/Allocator.Tpo -c -o Allocator.lo Allocator.cc
../../libtool: line 2089: Allocator.cc: command not found
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -D_LARGEFILE64_SOURCE=1 
-D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT -Dlinux 
-I/usr/include/tcl8.4 -g -O2 -pipe -Wall -Werror -O3 
-feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -MT 
Allocator.lo -MD -MP -MF .deps/Allocator.Tpo -c ""  -fPIC -DPIC -o 
.libs/Allocator.o
g++: : No such file or directory
g++: no input files
make[4]: *** [Allocator.lo] Error 1
make[4]: Leaving directory 
`/home/arno/build-area/trafficserver-2.1.9-unstable/lib/ts'
make[3]: *** [all] Error 2
make[3]: Leaving directory 
`/home/arno/build-area/trafficserver-2.1.9-unstable/lib/ts'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory 
`/home/arno/build-area/trafficserver-2.1.9-unstable/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/arno/build-area/trafficserver-2.1.9-unstable'
dh_auto_build: make -j1 returned exit code 2
{code}

This is the same output for the untouched tarball (i.e. without running 
_autoreconf_):

{code}
make[4]: Entering directory 
`/home/arno/build-area/trafficserver-2.1.9-unstable/lib/ts'
/bin/bash ../../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I.   
-D_LARGEFILE64_SOURCE=1 -D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT 
-Dlinux -I/usr/include/tcl8.4  -g -O2 -pipe -Wall -Werror -O3 
-feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -MT 
Allocator.lo -MD -MP -MF .deps/Allocator.Tpo -c -o Allocator.lo Allocator.cc
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -D_LARGEFILE64_SOURCE=1 
-D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT -Dlinux 
-I/usr/include/tcl8.4 -g -O2 -pipe -Wall -Werror -O3 
-feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -MT 
Allocator.lo -MD -MP -MF .deps/Allocator.Tpo -c Allocator.cc  -fPIC -DPIC -o 
.libs/Allocator.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -D_LARGEFILE64_SOURCE=1 
-D_COMPILE64BIT_SOURCE=1 -D_GNU_SOURCE -D_REENTRANT -Dlinux 
-I/usr/include/tcl8.4 -g -O2 -pipe -Wall -Werror -O3 
-feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -MT 
Allocator.lo -MD -MP -MF .deps/Allocator.Tpo -c Allocator.cc -o Allocator.o 
>/dev/null 2>&1
mv -f .deps/Allocator.Tpo .deps/Allocator.Plo
{code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to