On 6/29/09 3:26 PM, Stephen Henson via RT wrote:
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
The FIPS builds currently don't support cross compilation so this be of
much use in practice: they have to run a generate binary in order to
extract the signature during the linking process.
I'm sorry, I guess I'm not understanding what you're saying here.
If this step is run as part of the build process, then the binaries need
to be for the build host (and not the target host).
If on the other hand you're saying that this step isn't mandatory, then
can we add an additional target (like "make build-no-fips") that skips
this step altogether?
Thanks.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
