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 12:55:28 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	19
Message-ID:	<8lhec0$dap$1@nets3.rz.RWTH-Aachen.DE>
References:	<Pine DOT LNX DOT 4 DOT 21 DOT 0007241620460 DOT 1105-100000 AT roadrunner DOT grendel DOT net>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 964443328 13657 137.226.32.75 (24 Jul 2000 12:55:28 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	24 Jul 2000 12:55:28 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:
> On Sun, 23 Jul 2000, Eli Zaretskii spoke the following immortal words,
>> 
>> 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.

> Thanks, I am aware of this, but what I really would like to know, is *what
> are the functions* that I have to supply, Is there a list somewhere which
> would help me know what are the functions that I should supply if I want
> to port it to other UNIX flavours..

The DJGPP libc docs should you give you a good hint: if a function is
listed as 'not ANSI', you'll want to supply a fallback implementation.
Even more so it if it's not even POSIX.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -