Date: Thu, 3 Feb 2000 12:27:09 +0200 (WET) From: Andris Pavenis To: Mumit Khan , djgpp-workers AT delorie DOT com Subject: Re: (patch) updated protoize patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=windows-1257 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by delorie.com id FAA22453 Reply-To: djgpp-workers AT delorie DOT com Errors-To: dj-admin AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Wed, 2 Feb 2000 pavenis AT lanet DOT lv wrote: > 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 > As far as I looked with debugger (RHGDB under DOSEMU-0.99.13, Linux-2.2.15pre5) following procedure in protoize.c static const char * shortpath (const char *, const char *) seems to be broken when DJGPP is installed on different drive than the files I want to process with unprotoize.exe are located (eg. I used copy of DJGPP installed in D:/DJGPP and put test file on C:). shortpath() returns variable rel_buffer which contains nonsense in this case. I suspect that this problem may also be actual for Win32 ports as the situation perhaps is similar. Andris PS. Of course I used patched gcc-2.95.2.