Message-ID: <20000804080024.2307.qmail@web1611.mail.yahoo.com> Date: Fri, 4 Aug 2000 01:00:24 -0700 (PDT) From: Vikas Yadav Subject: Re: Uh oh. Another newbie. (Sorta...) To: djgpp AT delorie DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Reply-To: djgpp AT delorie DOT com Matt Lewandowsky wrote: > > OK. I have chosen a better failing program this time... (One that actually > demonstrates my problems.... Why didn't I think of that?) > > --- BEGIN SNIPPET --- > sh-2.03$ ./configure > loading cache ./config.cache > checking for a BSD compatible install... ./install-sh -c > checking whether build environment is sane... yes > checking whether make sets ${MAKE}... yes > checking for working aclocal... missing > checking for working autoconf... found > checking for working automake... missing > checking for working autoheader... missing > checking for working makeinfo... found > checking for gcc... no > checking for cc... no This always happens with me. It never..Never finds "gcc" in DOS/Win. Then I have to mannualy replace the vars in "configure" > configure: error: no acceptable cc found in $PATH > sh-2.03$ autoconf > configure.in:51: warning: AC_TRY_RUN called without default to allow cross > compi > ling > configure.in:55: warning: AC_TRY_RUN called without default to allow cross > compi > ling > sh-2.03$ ./configure > loading cache ./config.cache > checking for a BSD compatible install... d:/djgpp/bin/ginstall -c > checking whether build environment is sane... yes > checking whether make sets ${MAKE}... yes > checking for working aclocal... missing > checking for working autoconf... found > checking for working automake... missing > checking for working autoheader... missing > checking for working makeinfo... found > checking for gcc... gcc > checking whether the C compiler (gcc ) works... yes > checking whether the C compiler (gcc ) is a cross-compiler... no > checking whether we are using GNU C... yes > checking whether gcc accepts -g... yes > checking for a BSD compatible install... d:/djgpp/bin/ginstall -c > checking for Cygwin environment... no > Configuring for Unix binary > checking for initscr in -lncurses... no > checking for initscr in -lcurses... no > checking for initscr in -lcur_colr... no > configure: error: Cannot find any curses-type library > sh-2.03$ > --- END SNIPPET --- > > Now, how do I get PDCurses recognised? And you see why I've gotten into > the habit of running autoconf each time I start from a tarball... ;) And I > have gotten a few library sources compiled (such as libpcap). However, they > are useless till I can get their companion programs compiled (tcpdump for > one)... (grr... I hate computers...) > > Once my curses problem is solved, then I might be able to figger out how to > link in Watt-32 support. (Perl would be a nice one to have this support... > *drool* CPAN *drool*...) > > Thanks, > > --Matt > > P.S. Any clues from anyone on how to clean up those AC_TRY_RUN errors from > autoconf? They disturb me... I think I dreamt of them attacking me last > night... ;) > I never got success to run the *unmodified* configure scripts till date in DOS/Win. I guess Autoconf does not know anything about DOS so none of these scripts fit in the file system that DOS uses. I do not think you are using DOS as the "$" prompt is visible. Vikas Yadav __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/