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 Robert Buck <rb...@mathworks.com> on 2002/11/20 20:31:12 UTC

Help: Jaguar build failures

We have about 15 MacOSX machines in build and test and regardless of
which one I pick, I get link errors when building Xerces-C. The linker
errors are:

g++ -DMACOSX -dynamiclib   -o
/private/home/rbuck/tmp/testx/xerces-c-src2_1_0/lib/libxerces-c.dylib.21
.0 MACOSX/ASCIIRangeFactory.o MACOSX/AbstractDOMParser.o M

atypeValidator.o MACOSX/YearMonthDatatypeValidator.o MACOSX/sax2Dummy.o
-framework CoreServices  -lpthread  -L/usr/lib
ld: Undefined symbols:
___rtti_si
___builtin_delete
___builtin_new
___builtin_vec_delete
___builtin_vec_new
___cp_pop_exception
___cp_push_exception
___eh_alloc
___pure_virtual
___rtti_class
___rtti_user
___start_cp_handler
___throw
___uncatch_exception
_terminate__Fv
___eh_rtime_match
___tfi
_cout
_write__7ostreamPCci
___tfUi

Here is what I am doing:

    35  14:08   curl -o xerces-c-src2_1_0.tar.gz
http://xml.apache.org/dist/xerces-c/stable/xerces-c-src2_1_0.tar.gz
    36  14:08   gunzip xerces-c-src2_1_0.tar.gz
    37  14:09   tar -xvf xerces-c-src2_1_0.tar
    38  14:09   cd xerces-c-src2_1_0
    39  14:10   setenv XERCESCROOT `pwd`
    40  14:10   cd $XERCESCROOT/src/xercesc
    41  14:10   autoconf
    42  14:11   ./runConfigure -p macosx -c gcc -x g++
    43  14:12   gmake

These have all been recently upgraded to Jaguar (10.2), so I cannot rule
out the possibility that these are improperly configured. But neither
can I rule out the possibility that there is a problem with the Xerces
build scripts or makefiles. Not being at all familiar with MacOSX, could
someone shed some light as to what may be happening? Does Xerces support
Jaguar?

Thanks,

Bob


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org


Re: Help: Jaguar build failures

Posted by James Berry <jb...@criticalpath.com>.
Robert,

The following works fine for me on Jaguar systems:

mkdir testx
cd testx
curl -O 
"http://xml.apache.org/dist/xerces-c/stable/xerces-c-src2_1_0.tar.gz"
gnutar -xzf xerces-c-src2_1_0.tar.gz
cd xerces-c-src2_1_0
setenv XERCESCROOT `pwd`
cd src/xercesc
./runConfigure -p macosx -n native
make


On 11/20/02 11:31 AM, "Robert Buck" <rb...@mathworks.com> wrote:

> We have about 15 MacOSX machines in build and test and regardless of
> which one I pick, I get link errors when building Xerces-C. The linker
> errors are:
> 
> g++ -DMACOSX -dynamiclib   -o
> /private/home/rbuck/tmp/testx/xerces-c-src2_1_0/lib/libxerces-c.dylib.21
> .0 MACOSX/ASCIIRangeFactory.o MACOSX/AbstractDOMParser.o M
> 
> atypeValidator.o MACOSX/YearMonthDatatypeValidator.o MACOSX/sax2Dummy.o
> -framework CoreServices  -lpthread  -L/usr/lib
> ld: Undefined symbols:
> ___rtti_si
> ___builtin_delete
> ___builtin_new
> ___builtin_vec_delete
> ___builtin_vec_new
> ___cp_pop_exception
> ___cp_push_exception
> ___eh_alloc
> ___pure_virtual
> ___rtti_class
> ___rtti_user
> ___start_cp_handler
> ___throw
> ___uncatch_exception
> _terminate__Fv
> ___eh_rtime_match
> ___tfi
> _cout
> _write__7ostreamPCci
> ___tfUi
> 
> Here is what I am doing:
> 
>   35  14:08   curl -o xerces-c-src2_1_0.tar.gz
> http://xml.apache.org/dist/xerces-c/stable/xerces-c-src2_1_0.tar.gz
>   36  14:08   gunzip xerces-c-src2_1_0.tar.gz
>   37  14:09   tar -xvf xerces-c-src2_1_0.tar
>   38  14:09   cd xerces-c-src2_1_0
>   39  14:10   setenv XERCESCROOT `pwd`
>   40  14:10   cd $XERCESCROOT/src/xercesc
>   41  14:10   autoconf
>   42  14:11   ./runConfigure -p macosx -c gcc -x g++
>   43  14:12   gmake
> 
> These have all been recently upgraded to Jaguar (10.2), so I cannot rule
> out the possibility that these are improperly configured. But neither
> can I rule out the possibility that there is a problem with the Xerces
> build scripts or makefiles. Not being at all familiar with MacOSX, could
> someone shed some light as to what may be happening? Does Xerces support
> Jaguar?
> 
> Thanks,
> 
> Bob
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-c-dev-help@xml.apache.org
> 
> 

--
/**********************************
 James D. Berry
 mailto:jberry@criticalpath.com
 vox:503.265.1213 fax:503.222.3020
 **********************************/



---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org