Le 8 mai 08 à 15:18, Jay Levitt a écrit :
I just encountered #15085 (nmap 4.6 doesn't build when ccache is
enabled), and thought I'd try to fix it. The problem seems to be
that nmap's configure.ac explicitly tests for the presence of a file
"g++" in the path. Unfortunately, with ccache enabled, the $AC_WORD
goes from "g++" to "ccache g++", and there ain't no "ccache g++" in
our path.
My first step is always to make sure I can rebuild configure from
autoconf, so I did:
$ autoconf
$
But: now, configure ignores ccache! I'm running it with the same
options that macports originally ran it with:
$ ./configure --prefix=/opt/local --without-zenmap --mandir=$
{prefix}/share/man --infodir=${prefix}/share/info --with-openssl=/
opt/local --with-libpcre=/opt/local
Before I go traipsing through thousands of lines of shell scripts,
can anyone enlighten me on the interaction of the ccache port and
autoconf? How does it insert itself?
Jay Levitt
ccache is enabled through the configure script environment, for example:
DEBUG: Environment: CFLAGS='-pipe -O2' CPPFLAGS='-I/opt/local/include'
CXXFLAGS='-pipe -O2' CPP='ccache /usr/bin/cpp-4.0' CXX='ccache /usr/
bin/g++-4.0' F90FLAGS='-pipe -O2' LDFLAGS='-L/opt/local/lib' FCFLAGS='-
pipe -O2' OBJC='ccache /usr/bin/gcc-4.0' INSTALL='/usr/bin/install -c'
OBJCFLAGS='-pipe -O2' FFLAGS='-pipe -O2'
"MACOSX_DEPLOYMENT_TARGET"='10.5' CC='ccache /usr/bin/gcc-4.0'
Hope it helps,
Anthony.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
