Mail Archives: djgpp-workers/2004/01/08/05:33:01
On Thursday 08 January 2004 11:23, Eli Zaretskii wrote:
> > From: Andris Pavenis <pavenis AT latnet DOT lv>
> > 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.
In source directory it built Ok also for me (after some patches of course)
The same problem appears when I try to build development versions of GCC
(I tried gcc-3.4-20021216 from gcc.gnu.org snapshots directory)
It seems to be some problem with chdir() (from DJGPP libc.a) in some context
(maybe?), but as I said I didn't suceed to create simple example which fails
on XP. For example find41b.zip for clio.rice.edu was not Ok and rebuilding it
fixed the problems. I didn't rebuild for example bash then. At this moment
I'm back from holydays and don't have WinXP around (old Win9X and Linux
only), so I cannot test more.
Andris.
- Raw text -