Cannot build libssl.a in isolation: "make build_ssl" also builds apps about openssl HOT 6 CLOSED

In our build file (Makefile) templates, there are no build_ssl and build_crypto, so dunno how you ended up using them. There is a build_libs, though, did you try that one? It shouldn't cause the apps to be built (but if you run make test, that will indeed cause the app to be built, 'cause many of our tests depend on it).

from openssl.

From the top Makefile in the 1.0.2d release:

build_crypto:
        @dir=crypto; target=all; $(BUILD_ONE_CMD)
build_ssl: build_crypto
        @dir=ssl; target=all; $(BUILD_ONE_CMD)

These do cause apps to be built. Target build_libs also causes apps to be built, without invoking make tests anywhere. Not having much expertise in makefiles, I would suggest that target=all is causing make to ascend and build all from the top. At some point I may resort to patching this with target=libs to prevent this.

In our build process, we do invoke build tests later, but with bitcode versions of libssl.a and libcrypto.a already available from the initial build. Everything does work, it's just an administrative hassle to have the initial build FAIL HARD after producing the two outputs we want. We'd like it to stop and exit, nicely and neatly, after producing our *.afiles, so that we know there isn't an actual problem.

from openssl.

1.0.2d has been out of support for some time, and those targets no longer exist.

from openssl.

A legacy build is unfortunately necessary in this case.

from openssl.

then I'm afraid you will have to manually fixup the makefile to build just what you want. though , I just tried:

make build_libcrypto

on 1.0.2.d and it only appears to have built libcrypto.so and libcrypto.a

from openssl.

For me, sometimes it builds apps, sometimes it doesn't. It would take some investigation to figure out why. For now it looks like I can move forward to 13.0.3, where the target build_libs is reliably stopping after generating the lib*.a files. That solves it for me.

from openssl.