Mail Archives: djgpp-workers/1998/02/05/18:32:10
Eli Zaretskii wrote :
>
> On Thu, 5 Feb 1998, Robert Hoehne wrote:
>
> Let me remind you the Murfy's Law of Software Releases. One of its
Yes, I know it :-(
> More seriously, I think we need to wait for some time and gather user
> responses before we decide to make g++ supercede DJ's gxx.exe. For
OK, I will let it gpp.exe.
> > At first only a small change:
> >
> > [gxx]
> > LIBRARY_PATH=%/>;LIBRARY_PATH%
>
> Why is this needed? Does g++ barf on backslashes? If so, it should
Oh please sorry for it. I simply pasted it from the [gcc] part
and had in my mind to include there only the %DJDIR/lib directory
so I removed the rest (for instance the grx lib dir) but now I
see that I made it wrong.
Of course g++ knows about the backslashes and so on. What I only
wanted to say with the above was, that we must tell g++ where to
look for crt0.o and nothing else, since all the other paths are
hardcoded (via $DJDIR) also beside others the $DJDIR/lib, but this
directory is _not_ searched by default for the startfile and the
specs file.
> be changed to support them. Does it require the variable to end with
> a semi-colon, or be all lower-case? If so, why?
See above. Please excuse me, I'm very stressed at the moment.
> I think prior practice is also important. Since names like libstdcxx
> and libgpp were picked up a long time ago, I say let's stick with them.
OK, to remember the history of DJGPP I will leave them as they are.
> The error message is printed by PKUNZIP, right? InfoZip does the
I don't have pkunzip, I use a unzip from InfoZip which I compiled
sometimes myself (a long time ago).
> right thing (extracts it as g__.exe) and never complains.
No, my unzip simply prints an error does not extract it. But
probably I haven't the latest version.
Robert
- Raw text -