RE: xml-security-c1.4 and freebsd

[csross <cr...@hccs.com>]

Since I got the errors trying to build the latest versions (xerces and
xml-security), I"m trying xerces 2.8 and xml 1.4.  I just got this error and
you mention to check the logs but the config.log doesn't give a clue.

Any other ideas?



Scott Cantor wrote:
> 
>> last output lines:
>> [...]
>> checking for Xerces 2.x or 3.x headers in XERCESCROOT/include... found
>> checking for Xerces 2.x or 3.x library naming convention... unable to
>> determine
>> configure: error: cannot link to Xerces library
> 
> Check the log (jeesh, I wish configure would just *say* that when it
> errors
> out, it would save so much email).
> 
>> xerces is xerces-c-src_2_8_0 installed in /opt/shibboleth-sp
>> some env:
>> 
>> XERCESCROOT=/usr/local/src/xerces-c-src_2_8_0
> 
> That's not necessary for building xmlsec anymore, and you can use
> --with-xerces if you need to.
> 
>> CPPFLAGS=-I/opt/shibboleth-sp/include/xercesc/
>> LDFLAGS=-L/opt/shibboleth-sp/lib/
> 
> As a rule, NEVER manually set those to values that configure should be
> getting through "proper" options. It just confuses the scripts.
> 
>> I'm sure I'm doing something wrong. Unfortunately I'm a newcomer.
> 
> Well, the code you're trying to build is not supported on FreeBSD, so
> consider whether that's even something you can deal with anyway.
> 
> -- Scott
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/xml-security-c1.4-and-freebsd-tp17886242p24175679.html
Sent from the Apache XML - Security - Dev mailing list archive at Nabble.com.

RE: xml-security-c1.4 and freebsd

[csross <cr...@hccs.com>]

Thank you but after much searching for it on the list, I gave up last night. 
I was using the same paths that allowed me to successfully build the other
modules.  

I finally built all the pre-requisites from the same scripts but modified
the configure and prefix lines to use use the native /usr/sfw and
/usr/local/ instead of /opt/shibboleth-sp, and no LD_LIBRARY_PATH.  The
scripts are the on NativeSPSolaris10SourceBuild.  I used those versions of
the software as well.

I am ready to build the shibboleth application now.  I am going to post a
question concerning the flags in the configure script specified on your site
about if CFLAGS="-D_sparc_" CXXFLAGS="-D_sparc_ -library=Cstd,Crun"
LDFLAGS="-lz" is still required.

thank you



Scott Cantor wrote:
> 
> csross wrote on 2009-06-24:
>>  Anyone have an idea why this occurred?  I've posted the failure from
>> the config.log.
> 
> Same as always, your path is wrong. Regardless, the build bug was
> explained
> on the shibboleth-users list, and is easy to fix.
>  
> -- Scott
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/xml-security-c1.4-and-freebsd-tp17886242p24188556.html
Sent from the Apache XML - Security - Dev mailing list archive at Nabble.com.

RE: xml-security-c1.4 and freebsd

[Scott Cantor <ca...@osu.edu>]

csross wrote on 2009-06-24:
>  Anyone have an idea why this occurred?  I've posted the failure from
> the config.log.

Same as always, your path is wrong. Regardless, the build bug was explained
on the shibboleth-users list, and is easy to fix.
 
-- Scott

RE: xml-security-c1.4 and freebsd

[csross <cr...@hccs.com>]

Anyone have an idea why this occurred?  I've posted the failure from the
config.log.  

Thank you very much.



csross wrote:
> 
> Since I got the errors trying to build the latest versions (xerces and
> xml-security), I"m trying xerces 2.8 and xml 1.4.  I just got this error
> and you mention to check the logs.  It happened both with XERCESROOT and
> the --with-xerces flag 
> 
> checking for Xerces 2.x or 3.x headers in XERCESCROOT/include... found
> checking for Xerces 2.x or 3.x library naming convention... unable to
> determine
> configure: error: cannot link to Xerces library 
> 
> I see in the log its looking for library "ld: fatal: library -lxerces-3.0:
> not found"
> 
> I guess a fresh start tomorrow without trying to install the later
> versions first.
> 
> -Christine
> 
> 
> Scott Cantor wrote:
>> 
>>> last output lines:
>>> [...]
>>> checking for Xerces 2.x or 3.x headers in XERCESCROOT/include... found
>>> checking for Xerces 2.x or 3.x library naming convention... unable to
>>> determine
>>> configure: error: cannot link to Xerces library
>> 
>> Check the log (jeesh, I wish configure would just *say* that when it
>> errors
>> out, it would save so much email).
>> 
>>> xerces is xerces-c-src_2_8_0 installed in /opt/shibboleth-sp
>>> some env:
>>> 
>>> XERCESCROOT=/usr/local/src/xerces-c-src_2_8_0
>> 
>> That's not necessary for building xmlsec anymore, and you can use
>> --with-xerces if you need to.
>> 
>>> CPPFLAGS=-I/opt/shibboleth-sp/include/xercesc/
>>> LDFLAGS=-L/opt/shibboleth-sp/lib/
>> 
>> As a rule, NEVER manually set those to values that configure should be
>> getting through "proper" options. It just confuses the scripts.
>> 
>>> I'm sure I'm doing something wrong. Unfortunately I'm a newcomer.
>> 
>> Well, the code you're trying to build is not supported on FreeBSD, so
>> consider whether that's even something you can deal with anyway.
>> 
>> -- Scott
>> 
>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/xml-security-c1.4-and-freebsd-tp17886242p24184404.html
Sent from the Apache XML - Security - Dev mailing list archive at Nabble.com.