From: "Andreas Bauer" Newsgroups: comp.os.msdos.djgpp Subject: RE: GNU gettext problem Date: Wed, 28 Feb 2001 16:50:06 +0100 Organization: T-Online Lines: 33 Message-ID: <97j6tu$np9$01$1@news.t-online.com> References: <5BF60CD649EDD411A04600B0D049F53A09246C AT hydmail02 DOT hyd DOT wilco-int DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: news.t-online.com 983375615 01 24361 yl90R4VSTaKqT 010228 15:53:35 X-Complaints-To: abuse AT t-online DOT com X-Sender: 320036379939-0001 AT t-dialin DOT net User-Agent: Pan/0.9.1 (Unix) X-No-Productlinks: Yes To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Thanks very much for that reply. It explains a lot indeed. > 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. > http://www.delorie.com/djgpp/doc/ug/compiling/portgnu.html for all those > details. Have done so. Thanks. It basically says long file names are not supported and that you have to rename them with scripts, doesn't provide an example though on how to do it or who has done it before. 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. That really is painful for everyone involved. I'm thankful for further advice or examples! Andi. -- Andreas Bauer, baueran at in.tum.de Web: http://home.in.tum.de/baueran/