X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f Date: 08 Jan 2004 11:23:16 +0200 Message-Id: From: Eli Zaretskii To: Andris Pavenis CC: djgpp-workers AT delorie DOT com In-reply-to: <200401081012.08913.pavenis@latnet.lv> (message from Andris Pavenis on Thu, 8 Jan 2004 10:12:08 +0200) Subject: Re: Possible update of GCC-3.3.2 References: <200401081012 DOT 08913 DOT pavenis AT latnet DOT lv> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: Andris Pavenis > Date: Thu, 8 Jan 2004 10:12:08 +0200 > > 2) got strange error messages like 'sources are in directory foo, but cd foo > does not work', when foo was DOS absolute path without drive letter. > Workarounded that by editting Makefile to add /dev/c at start of path. > Unfortunatelly that happens in rather specific situation when cd fails with > ENOENT, but I was not able to find an simple example where it happens. > One package which has this problem was GDB-6.0 (configure in directory > libiberty run from toplevel make fails with that error at least if source > directory is different from build directory) As far as GDB is concerned, I've successfully built both GDB 6.0 and the current development CVS snapshot, but only from the source directory. (The patches to do that, which I sent to this list a week or so ago, are already in the GDB CVS.) I currently don't have time to debug and fix the build outside the source directory, especially not on Windows XP, sorry. Just keeping GDB in CVS buildable by DJGPP, and even that only on Windows 9x and only from the source directory, is all I can promise now and for the observable future.