[1017] in Kerberos-V5-bugs
Re: running configure from a symlink farm
daemon@ATHENA.MIT.EDU (Richard Basch)
Mon Jan 2 13:45:33 1995
Date: Mon, 2 Jan 1995 13:45:24 -0500
To: eichin@cygnus.com
Cc: cfields@MIT.EDU, krb5-bugs@MIT.EDU
In-Reply-To: [1016] krb5-bugs
From: "Richard Basch" <basch@MIT.EDU>
>> I made a symlink farm to krb5 sources and ran configure.
My usual procedure is to make a symlink farm, run util/reconf in that,
and then move to *another* directory for the build, and use configure
with the --srcdir option (although running configure with an absolute
or relative path should do the right thing as well.) This does mean
that you need sunmake or gnumake.
_Mark_
Actually, what we gave to Craig as V5 sources, already had the initial
steps performed:
(cd util/autoconf; ./configure; make); ./util/reconf --force
The problem is actually that "configure" does not try to remove the
Makefile before generating another one from Makefile.in, and he was
bitten by the fact that the top-level Makefile existed and was symlinked
into read-only space. It should be a quick fix to the
V5_AC_OUTPUT_MAKEFILE rule...
-Richard
