Hello Amos,
* Amos Jeffries wrote on Mon, May 04, 2009 at 03:16:50AM CEST:
> Yes it is Squid-3.
> The official snapshot bundle can be found at:
> http://www.squid-cache.org/Versions/v3/HEAD/
> The bundle is generated on another OS with older autoconf version that
> does not have this issue. The problem appears when this is bootstrapped to
> the newer autotools chain.
I can confirm the
config.status: executing libtool commands
/bin/rm: cannot remove `libtoolT': No such file or directory
issue. It is due to both the Libtool macros and the configure.in
defining $RM, and configure.in uses
AC_PATH_PROG(RM, rm, $FALSE)
whereas the Libtool macros expect "rm -f". One fix could be to
AC_PATH_PROG(RM, rm, $FALSE)
RM="$RM -f"
I agree that Libtool should probably document this RM usage.
> The linkage problem is then displayed by:
> mkdir test && cd test && ../configure --silent && make check
What problem is this? Can you post the libtool --mode=link command that
fails, plus all of its output?
I don't get as far as running "make check": "make all" already fails on
make[3]: Entering directory `/tmp/squid/squid-3.HEAD-20090507/build/src'
depbase=`echo mem.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
g++ -DHAVE_CONFIG_H
-DDEFAULT_CONFIG_FILE=\"/usr/local/squid/etc/squid.conf\"
-DDEFAULT_SQUID_DATA_DIR=\"/usr/local/squid/share\"
-DDEFAULT_SQUID_CONFIG_DIR=\"/usr/local/squid/etc\" -I../.. -I../../include
-I../../src -I../include -I../../lib -I../src -I/usr/include/libxml2 -Werror
-Wall -Wpointer-arith -Wwrite-strings -Wcomments -g -O2 -MT mem.o -MD -MP -MF
$depbase.Tpo -c -o mem.o ../../src/mem.cc &&\
mv -f $depbase.Tpo $depbase.Po
../../src/mem.cc:38:24: error: ClientInfo.h: No such file or directory
../../src/mem.cc: In static member function 'static void Mem::Init()':
../../src/mem.cc:424: error: 'ClientInfo' was not declared in this scope
make[3]: *** [mem.o] Error 1
but that's presumably because I don't have all build-prereqs installed
(how would I get them, on a mostly-stable Debian)?
Thanks,
Ralf
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
