Re: cross-compiling the curl library for PPC?
Date: Sat, 29 Apr 2006 23:17:28 +0200 (CEST)
On Sat, 29 Apr 2006, Robert P. J. Day wrote:
>> cd /path/to/built/libssl
>> make install DESTDIR=/tmp/whatever
> why, no, in fact, it doesn't, but thanks for playing. the fundamental
> problem is that, when you configure openssl, there are *two* destination
> directories you're allowed to specify:
Note how Brian used DESTDIR for the make install and it does not imply nor
require any prefix options at all.
> as a final attempt, i tried using the documented feature of
> configuring with
> CPPFLAGS="-I<path to headers>"
> LDFLAGS="-L<path to libs>"
> but that also failed
Why? How? I've used this approach myself a large number of times.
> in short, i'm willing to accept daniel's earlier position that what
> i'm trying to do simply can't be done without moving the build results
> of openssl around to "fake" an install setup that curl is happy with.
That's not what I said. I said *one way* to do it would be to move the files
around to make them end up in a install-like tree.
> i think that's annoying but i'm willing to live with it if that's reality.
> but i don't think what i'm doing is that outrageous and, more to the point,
> it might be helpful if that was more clearly documented in the INSTALL file.
The INSTALL file mentions what it does because
1 - that's the intructions I've been given from friendly people
2 - they have proven to work for numerous people (including myself)
I'm not saying the configure is perfect or that there isn't any flaws we can
fix, but the vague phrase "it doesn't work" is not really helping us to
understand how we would improve it.
-- Commercial curl and libcurl Technical Support: http://haxx.se/curl.htmlReceived on 2006-04-29