I'm trying to build OpenSSL 0.9.7b for VxWorks (Tornado 2.0.2 for PowerPC 860) on a Windows XP host and I ran into some problems. I did the following:
0) Installed Tornado 2.0.2 (a while ago, but noted just to be thorough). 1) Installed cygwin. 2) Launched cygwin. 3) Un-targz'd OpenSSL 0.9.7b into "/tmp" (which created "/tmp/openssl-0.9.7b"). 4) Added a vxworks-ppc860 line to the OpenSSL Configure script (like the 405 line except -DCPU=PPC860). 5) Typed "./Configure vxworks-ppc860". This completed successfully. 6) Typed "make". This failed with the following output: making all in crypto... make[1]: Entering directory `/tmp/openssl-0.9.7b/crypto' ccppc -I. -I.. -I../include -DOPENSSL_SYSNAME_VXWORKS -DOPENSSL_THREADS -DOPENSSL_NO_KRB5 -g -msoft-float -DCPU=PPC860 -I/target/h -c -o cryptlib.o cryptlib.c make[1]: *** [cryptlib.o] Error 255 make[1]: Leaving directory `/tmp/openssl-0.9.7b/crypto' make: *** [sub_all] Error 1 I also tried defining WIND_BASE (C:\Tornado in my case which turns into /cygdrive/c/Tornado in cygwin), WIND_HOST_TYPE (x86-win32), and adding $WIND_BASE/host/$WIND_HOST_TYPE/bin to PATH in hopes that it would use the PowerPC 860 GCC/etc instead of the default one. When I re-did step 6 from above, make fails immediately because it doesn't seem to like the "Makefile" symlink/shortcut the Configure script made. Targeting Makefile.ssl directly also fails due it not finding /bin/sh (which is there). I searched the OpenSSL archives and people seem to getting a lot further so I'm assuming it is just something simple that I'm either missing or doing incorrectly. Is there a document or something describing the steps people used to get OpenSSL building with VxWorks? A more general question I have is how do people typically integrate OpenSSL with the VxWorks build process. Do people build OpenSSL manually on its own then just copy over the header files and built library(s) into their VxWorks build tree and use Tornado to build with the rest of their VxWorks-based code? Or are the OpenSSL sources built along with the other VxWorks stuff via normal Wind River BAT file build scripts? Or are the OpenSSL sources just added directly to the Tornado project and built that way? One more question I had is how do people typically integrate OpenSSL into their source control system (e.g. CVS)? Do people import the whole source tree or only certain pieces. I typically import the whole tree for external components and build them directly from source, but I noticed the OpenSSL Configure script creates symbolic links (Windows shortcuts in cygwin), which aren't normally supported by things like CVS. Thanks in advance for any help. BTW...Please let me know if there is a more appropriate list for this kind of stuff. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
