[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
RE: [xml] Use of 'strdup' in xmlmemory.c?
- From: "Henke, Markus" <Markus_Henke ordat com>
- To: "'xml gnome org'" <xml gnome org>
- Cc: "'veillard redhat com'" <veillard redhat com>
- Subject: RE: [xml] Use of 'strdup' in xmlmemory.c?
- Date: Mon, 10 Dec 2001 10:25:06 +0100
> -----Original Message-----
> From: Daniel Veillard [mailto:veillard redhat com]
> Sent: Friday, December 07, 2001 6:59 PM
> To: Henke, Markus
> Cc: 'xml gnome org'
> Subject: Re: [xml] Use of 'strdup' in xmlmemory.c?
>
>
> On Fri, Dec 07, 2001 at 06:41:01PM +0100, Henke, Markus wrote:
> > Hello,
> >
> > i'm trying to compile libxml2 on MPE i/X 6.0 (and that is a pretty
> > adventure, btw... 8)
>
> Well as long as you have an ansi compiler this should not be that
> hard (this uses ASCII for C strings encoding I hope).
Hope so, and indeed i'm a big step up the ladder since i've found
a workeround for a parser bug in HP C/iX compiler (see coming
post regarding that subject...).
But there is still a major problem that lets the './configure' skript
generate inapplicable header files:
(From HP 3000 MPE/iX porting guide)
"At link time, unresolved external symbols are not returned as an error
condition because MPE supports run-time binding to external libraries."
The result is that './configure' find each and every function that it
scans, so the HAVE_... macros are all defined (many of them erroneously).
At least IMHO there is a coherence...
> > That platform doesn't provide a 'strdup()'-function, which
> is a pitty but OK
> > inasmuch as it's not ANSI conform (AFAIK).
>
> Yup, I used to work on a DecStation which hadn't it either
>
> > So, HAVE_STRDUP if *undefined* in "config.h", trio
> support is *enabled*
> > in "xmlversion.h" (although i don't know if trio cares
> about 'strdup()').
>
> I don't think so.
>
> > 669: xmlStrdupFunc xmlMemStrdup = (xmlStrdupFunc) strdup;
> > 670: #endif
> >
> > I'm not sure, but could it be that this is a vioalation of
> the portability
> > rules of libxml?
>
> Yep, it's bad replace it with
>
> xmlStrdupFunc xmlMemStrdup = (xmlStrdupFunc) xmlStrdup;
Yep, done that...
> BTW with more recent version of the libraries it's in globals.c
Yes, i know i'm somewhat afterwards (2.4.6), but i fear that it
makes no sense to switch to a recent version as long as i havn't
solved the basic problems.
> Daniel
Thanx, Markus
> --
> Daniel Veillard | Red Hat Network https://rhn.redhat.com/
> veillard redhat com | libxml Gnome XML XSLT toolkit
http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]