Mail Archives: djgpp/1998/04/17/18:08:32
> The replacement linker from RSXNT does not work correctly with the -s
> linker switch: the solution is simply not to use this linker when
> building DOS programs. This is explained in the Allegro FAQ, btw.
Did that - no change.
> i dont think your path will work.
> it should look more like this.
> PATH"%PATH%;D:\DJGPP\BIN;D:\RSXNTDJ\BIN"
> keep me posted. i am very interested
> in using rsxntdj.
Did that - still no change.
I've poked and prodded just about everything I could. How the hell did
you guys get rsxntdj to work? Is it completely incompatible with gcc
2.8.0? If so, is the author working on an update? The only things
rsxntdj wanted me to change was the .env file, which I did, the ld,
which I did (but later undid), and the autoexec.bat, which I did in
about every format I can think of. What's missing? None of the demo's
will complete a compile, and lfn=y or n doesn't affect it. At least
DJGPP compiles without an error, but RSXNTDJ is just dead weight on my
harddrive. Anyone using it with success with djgpp with gcc 2.8.0? If
so, I'd appeciate autoexec.bats, .env files, suggestions, etc...
BTW - why does the man say gcc -v should get:
C:\WINDOWS>gcc -v
Reading specs from d:\rsxntdj\lib\specs <--back slashes
gcc version 2.7.0 something something
and I get:
C:\WINDOWS>gcc -v
Reading specs from d:\rsxntdj/lib/specs <--forward slashes
gcc version 2.8.0
???
Thanks,
Mike
- Raw text -