On 10/16/2009 11:28 AM, CB wrote: > Follow on information; > > I was able to get the host shlibsign to run by editing the sign.sh > script, end commenting out all the environment variables it exports, > which pointed into cross-compiled libraries. Yes, the problem was your host was picking up the cross libraries you just built. For cross compiling this is acceptable.
If you are getting that far, you are pretty much on your way to a complete build. If your target has a born shell and I think sed, you should be able to copy your build tree to your target machine and run all.sh (which should test your built binaries.). As wtc meantioned, the .chk files are for FIPS mode. You'll need them for your tests > So, the host version was > able to run and process the files it needed to. Is that going to > break anything on the target? > No, the .chk file format is cross platform. You should be able to generate .chk files on any platform and have them work on a target. The only potential problem is if the target platform mangles the .so files somehow. In that case you will have to regenerate the .chk files with shlibsign. You can do that on the target with the shlibsign you just built. bob
-- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
