Remi Pommarel <r...@triplefau.lt> writes: > On Thu, Sep 17, 2015 at 03:08:25PM -0700, Junio C Hamano wrote: >> That is, for most people, linking with -lcrypto was sufficient, but >> some people needed to grab things from -lssl when they need to do >> so, because things in -lcrypto referred to what was only in -lssl. > > Oh I see what you mean, I misinterpreted what NEEDS_SSL_WITH_CRYPTO > does. > > The problem on static compiled target is that libcurl.a got linked with > libssl symbols.
I think I said this already, but I found these bits from your patch - $(LIBS) $(CURL_LIBCURL) $(EXPAT_LIBEXPAT) + $(CURL_LIBCURL) $(EXPAT_LIBEXPAT) $(LIBS) that first uses libcurl and then libs (which has ssl bits) totally sensible. Shouldn't that be sufficient? > The proper variable I should have used is > NEEDS_SSL_WITH_CURL. But this variable is not setted on Linux and not > configurable,... Really? Anything is configurable from your config.mak, I would have thought. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
