You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by Jorge Pozo Ramirez <j....@externo.mju.es> on 2001/12/14 13:31:44 UTC
Xerces-C 1.6 and SCO OpenServer
Greetings, people.
Once again I managed to compile succesfully the latest Xerces
source-code (1_6_0) on SCO OpenServer 5.0.4. (with UnixWare OSR Compat
package).
For now, all executables developed here written for 1.5 worked nicely
with 1.6.
Attached I include a diff file with the few changes i had to write,
(most related to makefiles and threading model).
I only modified code for building the Xerces main library. For building
the samples, analog changes must be done to '$XERCESCROOT/samples/configure'
and '$XERCESCROOT/samples/Makefile.incl' files, like the ones done at
'$XERCESCROOT/src' files.
Best regards.
Jorge
Jorge Pozo Ramírez
Accenture - Spain
Technology Consulting Services
Government GMU
email: jorge.pozo.ramirez@accenture.com
------------------------------------------------------------
Subdirección General de Informática
- Ministerio de Justicia -
Madrid, España
email: j.pozo@externo.mju.es
Tel: 913902646
**********************************************************************
Este mensaje ha sido analizado con una herramienta de
deteccion de virus para su seguridad.
Ministerio de Justicia
www.mju.es
**********************************************************************
Re: Xerces-C 1.6 and SCO OpenServer
Posted by Jorge Pozo Ramirez <j....@externo.mju.es>.
Yep, this change, and other ones, are specifically for SCO, (see for
example the change for IconvTransService.cpp), and will probably scrap true
Unixware compilation. I submitted the patch only for reference to SCO users,
but it cannot be applied 'as is' to the source code. I was wondering to open
a new port called SCO, and add it to all sourcecode, but it seems to be a
waste of time, as 99% of the port is identical to Unixware, and there are
very few users of SCO left.
The main difficulty i found on SCO is the lack of pthread capabilities, so I
have to build in no theads mode.
Jorge.
> Jorge,
>
> In your diff, you have
> +++ xerces-c-src1_6_0/src/Makefile.incl Fri Dec 14 12:48:42 2001
> @@ -136,27 +136,27 @@
> #=============== UNIXWARE SPECIFIC OPTIONS =========================
> ifeq (${PLATFORM}, UNIXWARE)
> ifeq (${CXX}, g++)
> - PLATFORM_COMPILE_OPTIONS = -fPIC -D${PLATFORM} -D_REENTRANT
> + PLATFORM_COMPILE_OPTIONS = -fPIC -D${PLATFORM} -DAPP_NO_THREADS
> :
>
> Will it break other UNIXWARE users who want to build a thread-enabled
library??
>
> Since I am not an UNIXWARE users, need other UNIXWARE developers' advice
before
> I can commit your patch.
>
> There is a build instruction section:
> http://xml.apache.org/xerces-c/build-winunix.html#faq-5 to show users how
to
> build a single threaded library on various UNIX platforms. Should we add
> UNIXWARE instruction to that section instead of modifying Makefile.incl??
>
> Tinny
>
> Jorge Pozo Ramirez wrote:
>
> > Greetings, people.
> >
> > Once again I managed to compile succesfully the latest Xerces
> > source-code (1_6_0) on SCO OpenServer 5.0.4. (with UnixWare OSR Compat
> > package).
> >
> > For now, all executables developed here written for 1.5 worked
nicely
> > with 1.6.
> >
> > Attached I include a diff file with the few changes i had to write,
> > (most related to makefiles and threading model).
> > I only modified code for building the Xerces main library. For
building
> > the samples, analog changes must be done to
'$XERCESCROOT/samples/configure'
> > and '$XERCESCROOT/samples/Makefile.incl' files, like the ones done at
> > '$XERCESCROOT/src' files.
> >
> > Best regards.
> >
> > Jorge
> >
> > Jorge Pozo Ramírez
> > Accenture - Spain
> > Technology Consulting Services
> > Government GMU
> > email: jorge.pozo.ramirez@accenture.com
> > ------------------------------------------------------------
> > Subdirección General de Informática
> > - Ministerio de Justicia -
> > Madrid, España
> > email: j.pozo@externo.mju.es
> > Tel: 913902646
> >
> > **********************************************************************
> > Este mensaje ha sido analizado con una herramienta de
> > deteccion de virus para su seguridad.
> >
> > Ministerio de Justicia
> > www.mju.es
> > **********************************************************************
> >
>
------------------------------------------------------------------------
> > Name: diffs.160
> > diffs.160 Type: unspecified type (application/octet-stream)
> > Encoding: base64
> >
>
------------------------------------------------------------------------
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
**********************************************************************
Este mensaje ha sido analizado con una herramienta de
deteccion de virus para su seguridad.
Ministerio de Justicia
www.mju.es
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
Re: Xerces-C 1.6 and SCO OpenServer
Posted by Tinny Ng <tn...@ca.ibm.com>.
Jorge,
In your diff, you have
+++ xerces-c-src1_6_0/src/Makefile.incl Fri Dec 14 12:48:42 2001
@@ -136,27 +136,27 @@
#=============== UNIXWARE SPECIFIC OPTIONS =========================
ifeq (${PLATFORM}, UNIXWARE)
ifeq (${CXX}, g++)
- PLATFORM_COMPILE_OPTIONS = -fPIC -D${PLATFORM} -D_REENTRANT
+ PLATFORM_COMPILE_OPTIONS = -fPIC -D${PLATFORM} -DAPP_NO_THREADS
:
Will it break other UNIXWARE users who want to build a thread-enabled library??
Since I am not an UNIXWARE users, need other UNIXWARE developers' advice before
I can commit your patch.
There is a build instruction section:
http://xml.apache.org/xerces-c/build-winunix.html#faq-5 to show users how to
build a single threaded library on various UNIX platforms. Should we add
UNIXWARE instruction to that section instead of modifying Makefile.incl??
Tinny
Jorge Pozo Ramirez wrote:
> Greetings, people.
>
> Once again I managed to compile succesfully the latest Xerces
> source-code (1_6_0) on SCO OpenServer 5.0.4. (with UnixWare OSR Compat
> package).
>
> For now, all executables developed here written for 1.5 worked nicely
> with 1.6.
>
> Attached I include a diff file with the few changes i had to write,
> (most related to makefiles and threading model).
> I only modified code for building the Xerces main library. For building
> the samples, analog changes must be done to '$XERCESCROOT/samples/configure'
> and '$XERCESCROOT/samples/Makefile.incl' files, like the ones done at
> '$XERCESCROOT/src' files.
>
> Best regards.
>
> Jorge
>
> Jorge Pozo Ramírez
> Accenture - Spain
> Technology Consulting Services
> Government GMU
> email: jorge.pozo.ramirez@accenture.com
> ------------------------------------------------------------
> Subdirección General de Informática
> - Ministerio de Justicia -
> Madrid, España
> email: j.pozo@externo.mju.es
> Tel: 913902646
>
> **********************************************************************
> Este mensaje ha sido analizado con una herramienta de
> deteccion de virus para su seguridad.
>
> Ministerio de Justicia
> www.mju.es
> **********************************************************************
>
> ------------------------------------------------------------------------
> Name: diffs.160
> diffs.160 Type: unspecified type (application/octet-stream)
> Encoding: base64
>
> ------------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org