[openssl.org #1822] Issues w/ fips Makefile

[Philip Prindeville via RT]

The target:

fips_standalone_sha1$(EXE_EXT): sha/fips_standalone_sha1.c
        $(CC) $(CFLAGS) -DFIPSCANISTER_O -o $@ sha/fips_standalone_sha1.c 
$(FIPSLIBDIR)fipscanister.o

is built, but the extension is dropped when it's actually invoked:

fipscanister.o: fips_start.o $(LIBOBJ) $(FIPS_OBJ_LISTS) fips_end.o
        ...
        ./fips_standalone_sha1 fipscanister.o > fipscanister.o.sha1


should be "./fips_standalone_sha1$(EXE_EXT) ..." of course.

Also, in a cross-compiling environment, "CC" tends to default to the 
target machine.

If you're building intermediate binaries to be run as part of the build 
itself, these need to be indicated separately.

A common practice is:

HOSTCC?=$(CC)
...

fips_standalone_sha1$(EXE_EXT): sha/fips_standalone_sha1.c
        $(HOSTCC) $(CFLAGS) -DFIPSCANISTER_O -o $@ sha/fips_standalone_sha1.c 
$(FIPSLIBDIR)fipscanister.o



Thanks,

-Philip

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       openssl-dev@openssl.org
Automated List Manager                           majord...@openssl.org