* David Hill ([EMAIL PROTECTED]) wrote : > > ----- Original Message ----- > From: "Thom May" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, April 15, 2002 3:46 PM > Subject: Re: connect to listener warning message > > > > * David Hill ([EMAIL PROTECTED]) wrote : > > > > > > > > > > > > > > > > "David Hill" <[EMAIL PROTECTED]> writes: > > > > > > > > > Jeff, > > > > > > > > > > > of course :) (I also remember your other problem where I suggested > > > > > > running buildconf to pick up local libtool... what happened with > > > > > > that?) > > > > > > > > > > Just got around to trying that (long queue, what with a brand new > Apache > > > 2 > > > > > to play with :-). Yes, the latest libtool installed 1.4.2 and the > > > tarball > > > > > builds without a hitch. I saw a thread in dev@ talking about trying > to > > > > > resync with the public lib tool. Hopefully the libtool sync will > make it > > > > > into the next spin of the tarball. > > > > > > Found another oddity.... not sure where this one comes from, but doing > the > > > ./buildconf results in a srclib/apr/Makefile with top_builddir set to > > > nothing, which causes an error during install. Part of what I don't > > > understand is that without running ./buildconf, the build results in > > > top_builddir matching top_srcdir which means the the failing line in the > > > install phase is going to copy the header files that the previous line > just > > > copied........ > > > > Sander and I were looking at this earlier today - it's yet another > autoconf > > 2.53 "feature". Sander posted a diff to IRC that appears to be a > workaround > > for the problem, but the real fix appears to be along the lines of what > you > > suggest - we should always use the builddir unless it is unset. It should > > eliminate a lot of redundancy, and be a bit more fail proof too. > > Thoughts? > > If you are suggesting adding a simple check to the Makefile to test if > top_builddir is set before doing the copy, then I am fine with that. If you > are suggesting dropping the top_srcdir copy and only doing hte top_builddir > copy, then there may be an issue.... as that is currently where I am getting > at least one copy of the include files installed into the output tree > > Dave Just the check, yes. -Thom
-- Thom May -> [EMAIL PROTECTED] "We shall not make Britain's mistakes. Too wise to try to rule the world, we shall merely own it". --Ludwell Denny
