Mail Archives: djgpp/2000/08/03/16:10:19
---=-=---------====--=--===--==-=-=---=---=-=-==-=
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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
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... ;)
At 10:55 PM 8/2/00, Eli Zaretskii wrote:
>On Wed, 2 Aug 2000, Matt Lewandowsky wrote:
>
> > I can't get any configure scripts to recognise PDCurses (although
> > I installed 2.2, built 2.4, and then installed the prebuilt 2.4), nor
> can I
> > figure out how to get configure to recognise wattcp-32.
>
>I don't see any sign of these two failures in the trace of the
>configure run you posted. Where do you see the test for curses and
>network libraries in what the configure script does?
>
>In any case, the configure script leaves a file config.log which
>describes each failed test, including the source of the test programs
>it tries to compile and run. Look there for the clues why doesn't the
>script work as you think it should.
>
> > For example, this is the output from trying to compile pdksh under 9x. I
> > can't figure out quite why it's failing
>
>It fails because the sources seem to be broken for DJGPP:
>
> > jobs.c: In function `j_init':
> > jobs.c:237: `SIGCLD' undeclared (first use in this function)
> > jobs.c:237: (Each undeclared identifier is reported only once
> > jobs.c:237: for each function it appears in.)
>
>My guess is that the program uses SIGCLD without testing whether it is
>defined. DJGPP doesn't support the SIGCLD signal, so signal.h doesn't
>define it.
>
>The usual way to do this portably is like this:
>
> #ifdef SIGCLD
> ... code that uses SIGCLD ...
> #endif
>
>However, since this program seems to be a shell, it is possible that
>without SIGCLD some major features (like job control, as the name of
>the source file suggests) will not work. It's even possible that
>other, unrelated features will break. I suggest to browse through the
>sources and see what else depends on SIGCLD.
>
> > but under "pure" DOS (my usual environ), it won't even get through
> > ./configure.
>
>Probably due to long file-name problems with files like config.h.in.
>
> > (BTW, for the configure option specified, mmap() and flock() are
> > required. I have no clue if they are implemented in DJGPP...)
>
>The configure script detected, correctly, that they are not present in
>the library. I would expect a package that tries to find them at
>configure time to be able to provide a fallback. If you want to see
>what the package will do without mmap and flock, grep the sources for
>HAVE_MMAP and HAVE_FLOCK.
>
> > sh-2.03$ autoconf
> > configure.in:257: warning: AC_TRY_RUN called without default to allow
> cross
> > compiling
>
>I'm not even sure why did you need to run Autoconf. I would simply
>run the configure script supplied with the package.
>
>Note that I know nothing at all about this particular package; all I
>said above is from general knowledge of the configure machinery.
---=-=---------====--=--===--==-=-=---=---=-=-==-=
Content-Type: application/pgp-signature
-----BEGIN PGP MESSAGE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBOYnRROoMko8dOmunEQLmRgCdGM9Sjx1wQeREqx+QN4RGUhKnp20An3UW
oCfECMaTBLZNv3jlHDGOit1L
=7RS7
-----END PGP MESSAGE-----
---=-=---------====--=--===--==-=-=---=---=-=-==-=--
- Raw text -