Hi folks,

Similar to an email just sent, I'm trying to cross compile (except for an
Analog Devices Blackfin, uclinux based, little-endian).

We're stuck with openssl 0.9.8, so I'm trying to build openssl-fips-1.2.2.

Here's the steps being executed for openssl-fips-1.2.2:

        (set -e ; \
                export MACHINE=generic32 ; \
                export RELEASE=2.6.34 ; \
                export SYSTEM=Linux ; \
                export HOSTCC=gcc ; \
                export INSTALL_PREFIX=$(STAGEDIR) ; \
                export FIPS_SIG=$(ROOTDIR)/lib/openssl-fips/incore; \
                export CROSS_COMPILE="bfin-linux-uclibc-"; \
                ./config fipscanisterbuild no-asm ; \
                make -j1 ; \
                make -j1  install )

FIPS_SIG is pointing to the incore script downloaded from
https://www.openssl.org/docs/fips/incore.gz.

The Makefile terminates with:

                ./libcrypto.so.0.9.8: Not a FIPS executable

By setting DEBUG=1 in the incore script, I see:
FIPS_rodata_end=
FIPS_rodata_start=
FIPS_signature=
FIPS_text_end=
FIPS_text_start=
FINGERPRINT_ascii_value=
DOTrodata=000CFF64
DOTrodata_OFF=000CFF64
DOTtext=0003CAB8
DOTtext_OFF=0003CAB8

Should openssl-fips be building libcrypto and libssl?  I thought those would
be built in step 2 from the openssl-0.9.8 source.

These are created successfully:
lib/openssl-fips/openssl-fips-1.2.2/fips/fipscanister.o.sha1
lib/openssl-fips/openssl-fips-1.2.2/fips/fipscanister.o


I feel like I'm missing something obvious, but I can't seem to find what I'm
missing.



--
View this message in context: 
http://openssl.6102.n7.nabble.com/Cross-compiling-1-2-2-for-the-Analog-Devices-Blackfin-tp48173.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           majord...@openssl.org

Reply via email to