Mail Archives: djgpp-workers/1998/02/04/18:17:33
Andrew Crabtree wrote :
>
> I think he is referring to the one that comes with djdev. I would suggest
> trying to move towards usung the new one, since it does not
I would prefer this too (thatswy I will include it in gpp280b.zip).
> get currenty. It does require the change to djgpp.env though.
At first only a small change:
[gxx]
LIBRARY_PATH=%/>;LIBRARY_PATH%
so it can find the specs and crt0.o, or we move these two files
in the directory, where gcc and gxx look for them by default, in
%DJDIR%/lib/gcc-lib/djgpp/2.80
but that's probably not possible, since this would need to move
those files (at least crt0.o) when the version of gcc will change.
> > call it gpp or something, so it doesn't overwrite the one that comes
> > with djdev.
> Yuck. That would mean that libg++.a became libgpp.a, and that before
> this, people thought that gxx was g++, but now we release a real port
Yes, this is confusing to me too
libstdc++.a -> libstdcxx.a
libg++.a -> libgpp.a
g++.exe -> gpp.exe
c++filt.exe -> cxxfilt.exe
I think we should come to one technique. Changing ++ to xx or pp, where
I prefer to change ++ to xx.
> > I also suggest to have a symlink to it called g++.exe,
> > for the benefit of LFN platforms.
> Good idea. I'll put this in the next PG++ snapshot as well.
Yes, that's a good idea, but then we should aware about reports
from error messages, when the user unzip gpp280b.zip, about the
invalid g++.exe (even when all the other is extracted OK, which
I tested).
Robert
--
******************************************************
* email: Robert Hoehne <robert DOT hoehne AT gmx DOT net> *
* Post: Am Berg 3, D-09573 Dittmannsdorf, Germany *
* WWW: http://www.tu-chemnitz.de/~sho/rho *
******************************************************
- Raw text -