> * In message <[EMAIL PROTECTED]> > * On the subject of "Re: new package proposal : CLISP" > * Sent on Tue, 9 Sep 2003 11:25:01 -0400 (EDT) > * Honorable Igor Pechtchanski <...> writes: > > > $ ls /usr/share/doc/Cygwin/ | wc -l > > 41 > > $ cygcheck -c | wc -l > > 206 > > > > so only 20% of packages supply this cygwin-specific README. > > Try also "ls /usr/doc/Cygwin/ | wc -l" -- some older packages still have > their Cygwin-specific docs there. That still doesn't cover all the > packages, but will probably bring the total to well over 50%.
nope. only 50 more packages there. > > > > > Last but not least, targetting cygwin-1.5.x is now a requirement > > > > > > > > Oh boy.... > > > > > > > > I upgraded to 1.5.3 last Friday and I cannot _configure_! > > > > the configure scripts fail with: > > > > > > > > ./configure --with-module=syscalls --with-module=regexp --build > > > > --fsstnd=redhat --with-module=dirkey --with-module=bindings/win32 > > > > --with-module=clx/new-clx > > > > --with-libsigsegv-prefix=/usr/local/libsigsegv-cygwin build-O > > > > ...... > > > > executing /cygdrive/d/gnu/clisp/current/build-O/avcall/configure > > > > --srcdir=../../ffcall/avcall --with-module=syscalls --with-module=regexp > > > > --with-module=dirkey --with-module=bindings/win32 --with-module=clx/new-clx > > > > --with-libsigsegv-prefix=/usr/local/libsigsegv-cygwin > > > > --cache-file=../config.cache > > > > configure: error: invalid package name: module > > > > > > > > the cause is an `expr' call which unexpectedly fails. > > > > if I add any other `expr' call right before the failing one, it works... > > > > > > > > advice?! > > > > > > Umm, sorry, I'm not as configure-savvy as I'd like to be... Do you > > > use autoconf? > > > > yes. > > > > > If so, did you re-run it after upgrading? > > > > yes. > > > > > It would help knowing which versions of autotools you have installed. > > > > autoconf 2.57a-1 OK > > automake 1.7.5a-1 OK > > Aren't those "test" versions? Do you get the same problem with the > "curr" ones? In any case, I'll just let some autotool expert (Chuck?) > speak up on this one. this, I think, is irrelevant. the problem appears to be no the configure scripts, but the _intermittent_ failure of `expr'. it is conceivable that a full clean re-build of sh-utils (of which `expr' is a part) might fix the problem. -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> He who laughs last thinks slowest.
