<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
I just encountered <a href="https://trac.macports.org/ticket/15085">#15085</a>
(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.<br>
<br>
My first step is always to make sure I can rebuild configure from
autoconf, so I did:<br>
<br>
<tt>$ autoconf<br>
$<br>
</tt><br>
But: now, configure ignores ccache! I'm running it with the same
options that macports originally ran it with:<br>
<br>
<tt>$ ./configure --prefix=/opt/local --without-zenmap
--mandir=${prefix}/share/man --infodir=${prefix}/share/info
--with-openssl=/opt/local --with-libpcre=/opt/local<br>
</tt><br>
<br>
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?<br>
<br>
Jay Levitt<br>
</body>
</html>