d 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-sec
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
>> 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 co
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.
>
>
> 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 w
I'm not able to build xml-security-c version 1.4 in FreeBSD 7.0.
Source is downloaded from svn
command is:
./configure ./configure --without-xalan --prefix=/opt/shibboleth-sp
last output lines:
[...]
checking for Xerces 2.x or 3.x headers in XERCESCROOT/include... found
checking for Xerces 2.x o
