On Sun, 30 Apr 2006, Robert P. J. Day wrote:

> i would have thought exactly the opposite -- that it's a *very* common
> thing you'd need to be able to do.

Let me put it this way: curl has supported SSL this way since 1998 and we
haven't yet had a reason to provide these options you miss. And we've _never_
had the demand before...

> it would be a bad thing if, in the process of cross-compiling, the build
> process started picking up pieces of the native stuff sprinkled around the
> build system, perhaps getting the wrong version of stuff in the process.

Again, I would call that a major mess and a bad config in the user's system. I
don't think many users do things like that.

> and, no, you can't solve it by doing an "install", even a bogus install to
> get the right structure.

Yes you can. 'make install' is not a secret spell, it is just a series of
commands and of course you can do them manually.

>> I would call mixing native and cross-compiled libs/headers a very
>> weird system setup. But that's just me.
>
> i'm not aware that there *is* any other kind of system.

Wow! Then let me enlighten you: mostly when you build and install a
cross-compiler (environment), you make that use a totally separate lib and
include tree. I've worked with _numerous_ (>10) such installations over the
last decade, and I've never experienced someone who mix native and
cross-compiled libs/headers the way you seem to be doing. Then when you run
configure for the cross-compiler, it just _can't_ pickup anything that wasn't
built and provided for the cross-compiler. It just won't be able to confuse
for examples x86 libs with ppc libs.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html