Message-Id:	<200007222202.BAA02425@mailgw1.netvision.net.il>
Date:	Sun, 23 Jul 2000 01:01:40 +0200
To:	Kalum Somaratna aka Grendel <kalum AT lintux DOT cx>
X-Mailer:	Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
CC:	djgpp AT delorie DOT com
In-reply-to:	<Pine.LNX.4.21.0007221847330.1537-100000@roadrunner.grendel.net>
	(message from Kalum Somaratna aka Grendel on Sat, 22 Jul 2000 18:54:16
	+0600 (LKT))
Subject:	Re: Porting software using Autoconf? Easing the pain...
References:	<Pine DOT LNX DOT 4 DOT 21 DOT 0007221847330 DOT 1537-100000 AT roadrunner DOT grendel DOT net>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Date: Sat, 22 Jul 2000 18:54:16 +0600 (LKT)
> From: Kalum Somaratna aka Grendel <kalum AT lintux DOT cx>
> 
> 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.
> 
> What I am specificaly interested in is wether anyone knows any code or
> library which automatically would enable it's own strdup, strcpy etc
> versions on compile time and would make porting of software much easier
> using autoconf, rather than me writing all the replacement strdup, strcpy
> and other missing functions etc...

The usual way to do so is to supply a working strdup which is only
used when Autoconf doesn't find one in the target library.  That's
what GNU packages do.

- Raw text -