Compiling curl with static libs does not make much sense if the dependencies are not available too... so I suggest changing openssl to openssl[static-libs?] and similar with other deps...
I'm wondering what the future of static-libs is anyhow. I agree it doesn't make sense if its not propagated, but how about just dropping it altogether. Perhaps is my prejudice, but I don't see much of a point to static libs in general.
The background was compiling a static qemu-user (and there static is needed if you use it to chroot into an environment of a different architecture)...
(In reply to comment #2) > The background was compiling a static qemu-user (and there static is needed > if you use it to chroot into an environment of a different architecture)... aaahhh ... good point. Okay. I'll push through the static-libs to all the deps.
Please test curl-7.25.0-r1 which I just added to the tree. It propagates static-libs to as many dependencies as possible, ie the ones that have it. I've also added some extra ssl providers (see the CURL_SSL use expand flag), which always provide static-libs even without the flag since they are aimed at embedded systems. If this satisifes your needs, please close.
