Date: Tue, 4 Jan 2000 10:56:37 +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.12dbbf9daf2cddd4989721@news.creator.dp.ua>
Message-ID: <Pine.SUN.3.91.1000104105019.26733B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 4 Jan 2000, Mike Gee wrote:

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

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

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.