From 45502bfe19fb03c9f343b03fa6434ee0bece8428 Mon Sep 17 00:00:00 2001 From: Richard Levitte Date: Fri, 19 Feb 2016 22:02:41 +0100 Subject: Always build library object files with shared library cflags This takes us away from the idea that we know exactly how our static libraries are going to get used. Instead, we make them available to build shareable things with, be it other shared libraries or DSOs. On the other hand, we also have greater control of when the shared library cflags. They will never be used with object files meant got binaries, such as apps/openssl or test/test*. With unified, we take this a bit further and prepare for having to deal with extra cflags specifically to be used with DSOs (dynamic engines), libraries and binaries (applications). Reviewed-by: Rich Salz --- crypto/md5/Makefile.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'crypto/md5') diff --git a/crypto/md5/Makefile.in b/crypto/md5/Makefile.in index b1d98e15ae..aec94b6d6b 100644 --- a/crypto/md5/Makefile.in +++ b/crypto/md5/Makefile.in @@ -13,7 +13,7 @@ AR= ar r MD5_ASM_OBJ= -CFLAGS= $(INCLUDES) $(CFLAG) +CFLAGS= $(INCLUDES) $(CFLAG) $(SHARED_CFLAG) ASFLAGS= $(INCLUDES) $(ASFLAG) AFLAGS= $(ASFLAGS) -- cgit v1.2.3