Re: libcxa.so

[David J Craigon <da...@arabidopsis.info>]

You don't need the Intel compiler. Gcc is fine.

In my experience, due to the numorous variations in gcc version* and 
other differences between linux distributions, you're always best off 
compiling from source. It's very easy, and I've never had it fail on 
linux (no programming skill required). On the other hand I've never got 
a xerces-c binary package to work (although I haven't tried lately).

David

* To cut a long story short, even slight changes of C++ compiler version 
(like between gcc 3.2.0 and gcc 3.2.1, I hear), breaks all of the 
existing C++ code you've compiled. This is distinct from C, where code 
compiled with one C compiler will usually work with any other C 
compiler. This is why it's very difficult to produce "one binary fits 
all" packages.

mick wrote:

> Hi there,
>
> I'm fairly new to C++, and very new to Xerces.  I downloaded the 
> latest Proton binary (2.2.0) and tried to compile a very simple 
> example against it, using gcc (3.2).
>
> From what I can tell it fails on linking with the message
>
> /usr/bin/ld: warning: libcxa.so.1, needed by 
> /usr/local/lib/libxerces-c.so, not found (try using -rpath or 
> -rpath-link)
>
> Now I have determined that this library is from the intel compiler, 
> and if I were compiling with icc then I could understand the message.  
> But does this mean that to use xerces-c, even if you are not using 
> icc, you have to have the intel compiler package?  And if not, how do 
> I get around this dependency?
>
> I've searched the archives and found the posts by brice ruth and 
> gareth reakes, and I am going to download and attempt to use the 
> statically linked binary that gareth mentioned.  But I'd still like to 
> know if the intel compiler is required.
>
> Many thanks,
>
> Mick
>
>
> ---------------------------------------------------------------------
> 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

Re: libcxa.so

[mick <mi...@mailandnews.com>]

David, Brice and Neil, thank you all.  Gareth's binaries worked a treat, 
and I'll be less hesitant about compiling from source in future!

Cheers,

Mick

David J Craigon wrote:

> You don't need the Intel compiler. Gcc is fine.
>
> In my experience, due to the numorous variations in gcc version* and 
> other differences between linux distributions, you're always best off 
> compiling from source. It's very easy, and I've never had it fail on 
> linux (no programming skill required). On the other hand I've never 
> got a xerces-c binary package to work (although I haven't tried lately).
>
> David
>
> * To cut a long story short, even slight changes of C++ compiler 
> version (like between gcc 3.2.0 and gcc 3.2.1, I hear), breaks all of 
> the existing C++ code you've compiled. This is distinct from C, where 
> code compiled with one C compiler will usually work with any other C 
> compiler. This is why it's very difficult to produce "one binary fits 
> all" packages.
>
> mick wrote:
>
>> Hi there,
>>
>> I'm fairly new to C++, and very new to Xerces.  I downloaded the 
>> latest Proton binary (2.2.0) and tried to compile a very simple 
>> example against it, using gcc (3.2).
>>
>> From what I can tell it fails on linking with the message
>>
>> /usr/bin/ld: warning: libcxa.so.1, needed by 
>> /usr/local/lib/libxerces-c.so, not found (try using -rpath or 
>> -rpath-link)
>>
>> Now I have determined that this library is from the intel compiler, 
>> and if I were compiling with icc then I could understand the 
>> message.  But does this mean that to use xerces-c, even if you are 
>> not using icc, you have to have the intel compiler package?  And if 
>> not, how do I get around this dependency?
>>
>> I've searched the archives and found the posts by brice ruth and 
>> gareth reakes, and I am going to download and attempt to use the 
>> statically linked binary that gareth mentioned.  But I'd still like 
>> to know if the intel compiler is required.
>>
>> Many thanks,
>>
>> Mick
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>


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