Mail Archives: djgpp/2000/01/05/04:25:44
In article <Pine DOT SUN DOT 3 DOT 91 DOT 1000104105019 DOT 26733B-100000 AT is>, Tue, 4 Jan
2000 10:56:37 +0200 (IST), Eli Zaretskii says...
> > Which, come to think of it, led me to following question: how can I
> > override default "lib*.a" library naming convention?
>
> AFAIK, you can't. But I don't understand why/when would you want to. If
> the library is not called lib*.a, just don't use the -lfoo pseudo-option;
> instead, name the library's full name on the command line.
Uh-huh... Thanks. Just this simple. Feeling stupid :) I looked it up how
MGL guys did the build - they use custom GCC loader, which parses all lib
names by himself precisely this way, with full paths appended (it's
beyound me why they just didn't named libs properly). Looks a lot of
typing to me, better stick with renaming.
BTW this custom loader dumps libraries list to the command line twice a
row, as MGL libraries are interdependant. Does ld have any faculties to
allow linking such libs?
> In my experience, any LFN-related problems can be easily resolved without
> breaking anything else. Disabling LFN is an act of desperation, perhaps
> understandable when some newbie runs into these problems, but one which
> trained professionals should (IMHO) never resort to.
Agreed. But then, maybe DJGPP support is not the highest priority for MGL
developers; they probably didn't have time to make it right way or simply
forget in a hurry. They probably have enough problems just to keep MGL
portable and compatible on all those platforms from DOS to Linux to BeOS,
whatever it is :)
But for now some newbies on scitech.mgl newsgroup keep asking about
lstdcxx missing and the such. (BTW, I noticed posts from Brendan on this
subj dated early December). The problem is known but presumably not fixed
yet. DLed MGL last beta, will look what can be done.
--
Best regards, Mike
- Raw text -