Date:	Wed, 5 Jan 2000 13:08:36 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Mike Gee <mikegee AT creator DOT dp DOT ua>
cc:	djgpp AT delorie DOT com
Subject:	Re: Include Paths
In-Reply-To:	<MPG.12dd1f88b4bf31db989724@news.creator.dp.ua>
Message-ID:	<Pine.SUN.3.91.1000105130406.9018A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 5 Jan 2000, Mike Gee wrote:

> 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?

You can put such libraries inside a "-( ... -)" group.  See section 8.9 
of the FAQ for more details.

> > 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 could always ask here and get their solution in no time.

> 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).

We had a prolonged private exchange with Brendan after he posted his 
problem.  It turned out that MGL's compilation/link procedure overwrites 
djgpp.env with one that disables LFN.  When the stock version of 
djgpp.env was made read-only, the problems went away.

> DLed MGL last beta, will look what can be done.

Thanks, it would be great to get this nuisance out of people's way.

- Raw text -