Mail Archives: djgpp/2000/11/12/06:48:50
> From: "Edmund Horner" <ejrh AT paradise DOT net DOT nz>
> Newsgroups: comp.os.msdos.djgpp
> Date: Sun, 12 Nov 2000 22:13:18 +1300
>
> For example, W3C's libwww:
>
> 1. There are no DJGPP-specific instructions with this package.
Probably because no one bothered to port libwww, or didn't send the
patches to the libwww maintainers. Please consider sending them your
patches, once you get libwww working with DJGPP.
> I typically run 'bash ./configure'
This is almost the correct command. You need to set $pefix, like
this:
bash ./configure --prefix='${DJDIR}'
or like this:
bash ./configure --prefix='/dev/env/DJDIR'
(these two commands are equivalent, but for subtle purposes the second
one is slightly better).
> 2. Firstly, configure says it can't automatically recognise the host system.
> I usually alter the command line to: 'bash ./configure i386-pc-msdosdjgpp'.
> Is that right?
Yes, i386-pc-msdosdjgpp is right. However, latest versions of the GNU
configure script recognize DJGPP automatically. Perhaps libwww has an
old version of the config.guess script?
What does "bash ./config.guess" print? Also, see below, about uname.
> checking for gcc... no
> checking for cc... no
Do you have a file share/config.site under your top DJGPP installation
directory? If so, it should have arranged things so that gcc.exe is
found on your PATH. It works for me.
It's possible that it didn't work for you because you didn't use the
"--prefix" option to the configure script. Please try it and see if
it helps.
The file config.site comes with Bash 2.03 and later, please make sure
you don't use an old Bash port.
> ./configure: uname: command not found
Aha! This means you don't have Sh-utils installed, or somehow deleted
the `uname' utility from there. This is probably the reason why the
configure script doesn't recognize your system as DJGPP, that
recognition is based on what `uname' prints.
- Raw text -