[Openswan Users] 2.6.33 fix for compile failure without USE_EXTRACRYPTO=true

Paul Wouters paul at xelerance.com
Tue Feb 22 14:10:32 EST 2011


For those seeing this on openswan 2.6.33:

cc: /vol/git/openswan.git/OBJ.linux.x86_64/lib/libcrypto/libsha2/libsha2.a: No such file or directory
cc: /vol/git/openswan.git/OBJ.linux.x86_64/lib/libcrypto/libsha2/libsha2.a: No such file or directory
make[3]: *** [addconn] Error 1

You can work around this by setting USE_EXTRACRYPTO=true in Makefile.inc.

If you want to compile without these (eg to be FIPS compliant) then
apply the below patch and you can leave USE_EXTRACRYPTO=false

Note that previous versions of openswan used USE_EXTRACRYPTO=true and included
blowfish, twofish and serpent ciphers.

diff --git a/lib/libcrypto/Makefile b/lib/libcrypto/Makefile
index 601b2af..66d8bbe 100644
--- a/lib/libcrypto/Makefile
+++ b/lib/libcrypto/Makefile
@@ -17,10 +17,10 @@ OPENSWANSRCDIR?=$(shell cd ../..; pwd)
  srcdir?=$(shell pwd)/
  include ${OPENSWANSRCDIR}/Makefile.inc

-SUBDIRS=libaes libdes libmd5 libsha1 libmd2
+SUBDIRS=libaes libdes libmd5 libsha1 libsha2 libmd2

  ifeq ($(USE_EXTRACRYPTO),true)
-SUBDIRS+=libblowfish libtwofish libserpent libsha2
+SUBDIRS+=libblowfish libtwofish libserpent


More information about the Users mailing list