Mail Archives: djgpp/2000/01/04/02:55:28
In article <Pine DOT SUN DOT 3 DOT 91 DOT 1000103104450 DOT 14725B AT is>, Mon, 3 Jan 2000
10:45:11 +0200 (IST), Eli Zaretskii says...
> There's no CPLUS_LIBRARY_PATH, that's true. But the problem seems to
> be with header files, not with libraries, so this is irrelevant.
Just wait until it comes to linking :)
Which, come to think of it, led me to following question: how can I
override default "lib*.a" library naming convention?
I run into that problem time ago, when I just downloaded and installed
MGL and was unable to link nothing, until renaming relevant libs.
(Brendan, you better take a note of it, however cludgy it may look - you
probably will stumble into that one too). I run DJGPP via RHIDE
exclusively and use make only in rare cases, if it can be of any
difference. It's not really a stopper, I'm just curious.
> We had private exchange with Brendan on these issues, where we indeed
> established that MGL's batch files overwrite djgpp.env. This was
> responsible for several weird problems, like lack of support for long
> file names (because MGL's djgpp.env says LFN=n) which breaks C++
> compilation when file names like libstdcxx.a and streambuf.h are
> involved.
Yes, and as far as I can tell this LFN=n setting can be safely ignored.
MGL 4.05 was built using djgpp 2.01 (gcc 2.8 or 2.7 IIRC), and the
developers probably run into some problems with LFN.
I will ask about it in MGL newsgroup.
--
Best regards, Mike
- Raw text -