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/s
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
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
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:
>> [...]
>> ch
> 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
