Mail Archives: djgpp/1998/05/18/13:02:14
On Fri, 15 May 1998 04:17:17 GMT, harlequin AT tmbg DOT org (Chaos Harlequin)
wrote:
> c:/djgpp/bin/ld.exe -o /dev/null c:/djgpp/lib/crt0.o -Lc:/djgpp/lib
> -Lc:/djgpp/lib/gcc-lib/djgpp/2.80 -Lc:/djgpp/lib -v
> c:/djgpp/tmp/RHkaaaaa/ccaaaaaa1.o -Tdjgpp.djl -lgcc -lc -lgcc
> GNU ld version 2.8.1 (with BFD 2.8.1)
> c:/djgpp/bin/stubify.exe -v /dev/null
> Warning: input file is not COFF or stubbed COFF
> .exe: No such file or directory (ENOENT)
> stubify for djgpp V2.X executables, Copyright (C) 1995 DJ Delorie
>
> End of the sample
>
>
> I don't know where the last error message (with stubify.exe) comes
> from;
This is normal: the standard `specs´ file has an entry which calls
stubify.exe, and in the bug report this is done for the "file"
/dev/null.
> I tried generating a bug report just a minute ago and it did not
> give me this error. Strange...
Yes, this is strange. I'd say you have two different `specs´ files: one
of them came with djdev201.zip and is in your c:/djgpp/lib directory,
the other one came with gcc280b.zip and is in your
c:/djgpp/lib/gcc-lib/djgpp/2.80 directory. Try and delete/rename the old
specs file in the lib directory, and also the file djgpp.djl in the lib
directory. They were designed for gcc 2.7.x, but 2.8.x has a different
directory structure, so there are some problems now. The readme.djgpp
file for gcc 2.8.1 explains this in detail (but I'm not sure about gcc
2.8.0).
Regards...
Michael
- Raw text -