David,
The --libdir directive should define the -L compiler options.
Usually the all the libs are in /usr/local/lib or /lib but when you
cross compile projects the libs will be in a directory such as
/opt/mips_dev/lib. The configure scripts produce a Makefile
with hard coded -L directives as a mater of fact they way they
are hard coded it may even prove to be a problem when doing
a native compile. Autoconf should magically put the correct
-L directive in an environment variable. My experience with
autoconf is a bit old and my attack plan was to take the example
recipe file and fiddle with it until it works. :-)
Regards
John G
[EMAIL PROTECTED] wrote:
> Hi John,
>
> Thanks for the heads-up. Can you explain more what obeying the --libdir
> directive means, and how we can fix it? I have to confess I don't very
> much about autoconf. Our original configure script came directly from
> Xerces-C.
>
> Thanks,
>
> Dave
>
>
> John Gentilin
> <gentijo@eyecatc To: Xalan
><[EMAIL PROTECTED]>
> hing.com> cc: (bcc: David N
>Bertoni/CAM/Lotus)
> Subject: Xalan C++ Build problems
> 09/18/2001 12:20
> AM
> Please respond
> to xalan-dev
>
>
>
> I am trying to cross compile the Xalan C++ and I found a few issues
> in the Make script.
>
> 1) the configure script does not obey the --libdir directive
>
> 2) In the Platform Support directory, the byte order detection
> code is incorectly looking for XALAN_LITLE_ENDIAN instead
> of XALAN_LITTLE_ENDIAN (missing a T).
>
> Regards
> John G
