Date: Tue, 16 Sep 1997 15:48:40 +0300 (IDT) From: Eli Zaretskii To: Weiqi Gao cc: djgpp AT delorie DOT com, pdftex AT tug DOT cs DOT umb DOT edu Subject: Re: pdftex (was Re: Tex) In-Reply-To: <341DFDBE.C149521D@a.crl.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Precedence: bulk On Mon, 15 Sep 1997, Weiqi Gao wrote: > Sebastian Rahtz wrote in the pdftex list: > > > > I'd say, don't even try at this stage; Fabrice uses Visual C++, and i think > > that doing it with djgpp is going to be non-trivial. depends how hard > > you want to work... > I disagree. Most of the problems with porting a Unix program are common to NT and DJGPP (binary vs text I/O, drive letters and backslashes in pathnames, etc.). So code that compiles on NT should be a good starting point. > I ran into several problems. None of them are pdftex problems. I have > encountered: > 1. ac_include in Makefiles choking make. (changed them to > include) Please post the details, if you care to solve this. ac_include worked for me when I configured Web2c and Kpathsea. Using include instead is NOT the correct solution (see below). > 2. @top_srcdir@, @srcdir@, etc. not substituted in the make/*.make > scripts. (changed them all to either . or .., knowing this will cause > problems later) They don't need to be substituted, this is a consequence of the ac_include problem. These *.make files are included in the Makefile's when they are created by the configure step, and the substitution is done as part of the inclusion by ac_include. Since you changed ac_include to include, the substitution wasn't done. > 3. make would error out because it cannot find a certain file. > (moved files around so that the wrong Makefile can find them) Shouldn't happen either, but I cannot say more without seeing the details.