Mail Archives: djgpp/2001/02/28/14:22:25
> From: "Andreas Bauer" <just DOT another AT address DOT postoffice DOT net>
> Newsgroups: comp.os.msdos.djgpp
> Date: Wed, 28 Feb 2001 16:50:06 +0100
> > Note that the name "Makefile.in.in" is NOT valid under DOS. Therefore
> > it's been changed to Makefile.in-in. This is done so that compiling
> > packages is possible under both DOS and Windows (with and without LFN
> > support).
> I understand, but what can I as Unix developer do for the DJGPP folks? My
> project is generating the "configure" script from "configure.in", so
> while creating this configuration file the DJGPP ppl get the first
> errors... Once those files are created I could of course manually change
> the file names, even with a script, etc. But the DOS developers don't
> even get to see the "configure" script.
Could you please explain what is the problem you are trying to solve?
I've read your original message, and I still don't get what bothers
you with the configure scripts.
Many DJGPP ports of GNU utilities use the configure script to
configure and build the package with DJGPP tools, with minimal
> As I see it now, I can't have DJGPP people in my project involved
> anymore, cause they can't handle the GNU autoconf utilities anymore;
> gettext is just generating way too long file names.
I don't see why would you come to such a drastic conclusion. Quite a
few DJGPP ports of GNU software are gettext-ready, so whatever the
problems that are involved, they have been solved more than once.
- Raw text -