Re: [patch] jk 1.2.8 Build failure on linux (1 liner)

2005-02-01 Thread William A. Rowe, Jr.
Actually, I've noticed another build problem. The declaration of 'test' on HP/UX is actually a posix sh wrapper to the built in sh - which invokes test [EMAIL PROTECTED] Sadly this means that empty arguments to test are dropped, such that test -z results in an 'insufficient arguments' error to

Re: [patch] jk 1.2.8 Build failure on linux (1 liner)

2005-01-27 Thread William A. Rowe, Jr.
JFC - you missed something. I'm not speaking of Apache 2.0 ... this is in r.e. Apache 1.3 (native/jk/apache13) :) Bill At 05:38 AM 1/20/2005, jean-frederic clere wrote: William A. Rowe, Jr. wrote: I'm finding that @top_builddir@ isn't resolved when I run ./buildconf / ./configure against

Re: [patch] jk 1.2.8 Build failure on linux (1 liner)

2005-01-20 Thread jean-frederic clere
William A. Rowe, Jr. wrote: I'm finding that @top_builddir@ isn't resolved when I run ./buildconf / ./configure against apache1.3 apxs, so the libtool isn't resolved. The fix is trivial, use the same fixed top_builddir=.. as all the other /native/ directories used. -0: It would be better to

[patch] jk 1.2.8 Build failure on linux (1 liner)

2005-01-19 Thread William A. Rowe, Jr.
I'm finding that @top_builddir@ isn't resolved when I run ./buildconf / ./configure against apache1.3 apxs, so the libtool isn't resolved. The fix is trivial, use the same fixed top_builddir=.. as all the other /native/ directories used. It still confuses me why, when apxs defined the correct