Mail Archives: djgpp/1998/08/26/18:56:19
On 26 Aug 98 at 10:49, Salvador Eduardo Tropea (SET) wrote:
> "George Foot" <george DOT foot AT merton DOT oxford DOT ac DOT uk> wrote:
>
> > Finally, some programs may have internal bugs which cause them to
> > break on long filenames. An example is RHIDE, which tries to link in
> > the standard C++ library with "-lstdcx" when its real name is
> > "-lstdcxx". RHIDE is assuming that the name should be truncated. If
> > you follow the instructions to change its request to "-lstdcxx" then
> > the truncation (or lack of truncation) will fall down to the djgpp
> > functions and the presence/absence of LFN support. Provided you
> > followed the instructions above, you won't have problems any more.
>
> You are wrong George when RHIDE 1.4 was released the distributed library was
> called libstdcx.a, then when gpp280/1b.zip was released (later) the library
> was renamed to libstdcxx.a. I don't know why such a change, I never saw
> somebody complaining about 272 (and previous) using stdcx and not stdcxx,
> from the other hand all the weeks I see at least one person complaining about
> stdcxx.
Yes, what I said wasn't very accurate. Ultimately though the
problem is that the gpp distribution now uses LFNs while the default
RHIDE configuration assumes that it doesn't. I didn't mean that it
was RHIDE's fault -- it's obviously Microsoft's fault really. ;)
I think though that the change to gpp is sensible; otherwise people
from a Unix background might complain when they can't `-lstdcxx', if
their system supports LFNs. If all packages are converted to support
LFNs then there should be no problems, if people do as I suggested in
my last message. Unfortunately packages like RHIDE must be updated
when the other packages change; of course that's not their fault.
--
george DOT foot AT merton DOT oxford DOT ac DOT uk
- Raw text -