From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Porting software using Autoconf? Easing the pain...
Date: 24 Jul 2000 10:41:43 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 19
Message-ID: <8lh6h7$9pm$1@nets3.rz.RWTH-Aachen.DE>
References: <Pine DOT LNX DOT 4 DOT 21 DOT 0007221847330 DOT 1537-100000 AT roadrunner DOT grendel DOT net>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 964435303 10038 137.226.32.75 (24 Jul 2000 10:41:43 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 24 Jul 2000 10:41:43 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Kalum Somaratna aka Grendel <kalum AT lintux DOT cx> wrote:

> Some functions like strdup are not available on some platforms.
> So when GNU autoconf detects that it can set a particular #define, which
> says that strdup is not on that system. Then you can supply your own
> strdup function.

Yes. Most GNU packages do exactly that. The FSF actually maintains a
special mini library for this very purpose: a collection of stand-ins
or replacements for missing or unusable functions in the system
libc. It's called 'libiberty', for the fun of linking it by the gcc
option '-liberty'.

You'll find 'libiberty', or parts of it, in many GNU packages, as a
subdirectory. If you program is going to be GPLed, I think you can use
libiberty in it, and avoid implementing your own.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.