From: pavenis AT lanet DOT lv
Message-ID: <B0000118036@stargate.astr.lu.lv>
To: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>, djgpp-workers AT delorie DOT com
Date: Wed, 2 Feb 2000 18:53:33 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Subject: Re: (patch) updated protoize patch
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000119121342 DOT 9609e-100000 AT is>
In-reply-to: <Pine.HPP.3.96.1000119205812.12013C-100000@hp2.xraylith.wisc.edu>
X-mailer: Pegasus Mail for Win32 (v3.12b)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from Quoted-printable to 8bit by delorie.com id LAA04102
Reply-To: djgpp-workers AT delorie DOT com

Yesterday built next updated version of DJGPP port of gcc-2.95.2 (with 
protoize patches of course). But this time I didn't do native build under
Win95, but used cross-compiling under Linux. Anyway native compiler
for DJGPP built under Linux seems to work Ok.

Additionally I found a new problem with protoize and unprotoize:

When file I process with protoize or unprotoize file which is one the 
same drive as DJGPP is installed, both works Ok. When they are on a 
different drive they output something supid in dependencies. For 
example:

D:\TEMP\4>unprotoize djmerge.c
unprot~1.exe: compiling `djmerge.c'
unprot~1.exe: converting file `djmerge.c'
unprot~1.exe: warning: file `djmerge.c' already saved in `djmerge.c.save'
unprot~1.exe: `..//include/unÍ ' not converted
unprot~1.exe: `../erge.c.save' not converted
unprot~1.exe: `../erge.c' not converted

Or even something similar.  Is there any similar behaviour for Win32 
ports of gcc

Andris