Re: libexpat.so error building on Suse 9.2 64 bit.

"Edward R. Rubinsky" <edrubins@speakeasy.net> writes:
> >I've run into a similar error with other packages and the solution was
> >to set --with-expatlibdir=/usr/lib64. You might also get it to work
> >by adding a -L/usr/lib64 to CFLAGS.
>
> That did the trick, but still at least one question un-answered.
>
> >The problem is that the build is finding a 32bit compatibility version
> >of expat before it finds the proper 64bit version.
>
> If the default path for libraries is /usr/lib, as advertised why is
> it referencing any 64 bit libraries.

Well, you've got a 64bit system so you'd hope that you'd be building
64bit binaries in general ;-)

Honestly, I don't totally understand how it finds the paths and such,
but I think /usr/lib64 by default comes before /usr/lib when gcc and
friends are searching for libs.

I think the problems occurs because the configure system hard-codes
/usr/lib for expat instead of honoring the default (where it would
find another expat).

> And why did neon build without the same problem?

Presumably for the same reason that other pacakges Do The Right Thing
on 64bit Linux without extra tweaking.

+ seth

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 6 00:22:57 2005