I think I know the answer to this but I'm hoping I am wrong. I am building the FIPS Object Module v2.0 (a recent snapshot) on an x86-linux2 host for an embedded PowerPC target running NetBSD. There is a well-established and intricate build process already in place for the product, and I am trying to build the FIPS module outside of that process but using the same cross-compiler.
That existing build process puts the system include files in a special directory, which is passed to gcc with a -I. When I build the FIPS module, there are several environment variables that can be set in order to get the cross-compile to work, except for the location of those system include files(?). My question is whether I am missing something - i.e., an environment variable - that I can set to indicate the location of that directory, without impacting the (future) validated status of the module. Or is there a simpler solution I am overlooking? If not, I expect I will need to modify the Makefile, and thus invalidate the module... Kevin
