For now I simply renamed the function. We can look for the reason later.
I'd prefer to get ecpg release ready first. :-)
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Lin
On Fri, 2003-09-19 at 07:38, Michael Meskes wrote:
> I included strndup because some systems didn't seem to have it. Any idea
> what else I could do? Okay, I could rename it and use only the renamed
> function as it's just used internally.
>
> What surprises me is that it compiles fine for me desp
On Thu, Sep 18, 2003 at 06:53:00PM +0100, Oliver Elphick wrote:
> Line 138 begins the definition of strndup(). However, strndup() is also
> declared in string.h, which is included by this file. If I rename this
> function to estrndup() (and also where it is called, further down) the
> compilation
On Thu, 2003-09-18 at 19:25, Tom Lane wrote:
> Oliver Elphick <[EMAIL PROTECTED]> writes:
> > Line 138 begins the definition of strndup(). However, strndup() is also
> > declared in string.h, which is included by this file. If I rename this
> > function to estrndup() (and also where it is called,
Oliver Elphick <[EMAIL PROTECTED]> writes:
> Line 138 begins the definition of strndup(). However, strndup() is also
> declared in string.h, which is included by this file. If I rename this
> function to estrndup() (and also where it is called, further down) the
> compilation succeeds.
Hm, is st
