[openssl.org #26] 64 bit Suse Linux on PowerPC
Lutz, I pulled the SNAP - openssl-0.9.6-stable-SNAP-20020513.tar.gz I took out the config file and ftped it to the SUSE linux 64 bit system on powerpc and ran the build over again and all worked well. ./config correctly set the system makeworked make test worked make install worked Thanks. John -- Forwarded by John Bihlmeyer/Raleigh/IBM on 05/14/2002 08:30 AM --- Lutz Jaenicke via RT [EMAIL PROTECTED]@openssl.org on 05/12/2002 03:47:11 PM Please respond to [EMAIL PROTECTED] Sent by:[EMAIL PROTECTED] To:John Bihlmeyer/Raleigh/IBM@IBMUS cc:[EMAIL PROTECTED] Subject:[openssl.org #26] 64 bit Suse Linux on PowerPC Thanks. I have added a corresponding entry into config. Please check out a new snapshot for correct behaviour. Best regards, Lutz __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [openssl.org #26] 64 bit Suse Linux on PowerPC
Thank you Lutz and Tim. By configuring with the following: ./Configure linux-ppc I was able to run make successfully and then run make test and make install successfully as well. I was able therefore to successfully build, run the build verification tests and install on the 64 bit Suse Linux on powerPC. Now all we need to do is get ./config to recognize this environment as linux-ppc and we will be fine. Thanks again. John __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
[openssl.org #26] 64 bit Suse Linux on PowerPC
Thanks. I have added a corresponding entry into config. Please check out a new snapshot for correct behaviour. Best regards, Lutz __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
Re: [openssl.org #26] 64 bit Suse Linux on PowerPC
Thank you Lutz and Tim. By configuring with the following: ./Configure linux-ppc I was able to run make successfully and then run make test and make install successfully as well. I was able therefore to successfully build, run the build verification tests and install on the 64 bit Suse Linux on powerPC. Now all we need to do is get ./config to recognize this environment as linux-ppc and we will be fine. Thanks again. John Lutz Jaenicke via RT [EMAIL PROTECTED]@openssl.org on 05/09/2002 04:25:26 PM Please respond to [EMAIL PROTECTED] Sent by:[EMAIL PROTECTED] To:John Bihlmeyer/Raleigh/IBM@IBMUS cc:[EMAIL PROTECTED] Subject:[openssl.org #26] 64 bit Suse Linux on PowerPC [[EMAIL PROTECTED] - Thu May 9 22:13:32 2002]: I am trying to compile on a 64 bit Suse sles7 powerpc system. the error message indicates -m486 is an invalid compiler parameter. Anyone know the parameters I need to give ./config to get it to work for 64 bit Suse on a powerpc below are the results from running ./config without parameters and the results from running the make command. Operating system: ppc64-whatever-linux2 Configuring for linux-elf Obviously config mistakenly selects the linux-elf target that is used for x86 platforms. (This is a bug that has to be fixed.) Configure also contains an entry for linux-ppc, I however don't know whether it is suitable for 64bit PowerPC. Please try Configure linux-ppc directly instead of calling config and keep us updated, whether it works out. Best regards, Lutz __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
[openssl.org #26] 64 bit Suse Linux on PowerPC
Hello to all, I am trying to compile on a 64 bit Suse sles7 powerpc system. the error message indicates -m486 is an invalid compiler parameter. Anyone know the parameters I need to give ./config to get it to work for 64 bit Suse on a powerpc below are the results from running ./config without parameters and the results from running the make command. Thanks for all your help John running ./config gave me the following::: Operating system: ppc64-whatever-linux2 Configuring for linux-elf Configuring for linux-elf IsWindows=0 CC=gcc CFLAG =-fPIC -DTHREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DTERMIO -O3 -fomit-frame-pointer -m486 -Wall -DSHA1_ASM -DMD5_ASM -DRMD160_ASM EX_LIBS =-ldl BN_ASM=asm/bn86-elf.o asm/co86-elf.o DES_ENC =asm/dx86-elf.o asm/yx86-elf.o BF_ENC=asm/bx86-elf.o CAST_ENC =asm/cx86-elf.o RC4_ENC =asm/rx86-elf.o RC5_ENC =asm/r586-elf.o MD5_OBJ_ASM =asm/mx86-elf.o SHA1_OBJ_ASM =asm/sx86-elf.o RMD160_OBJ_ASM=asm/rm86-elf.o PROCESSOR = RANLIB=/usr/bin/ranlib PERL =/usr/bin/perl THIRTY_TWO_BIT mode DES_PTR used DES_RISC1 used DES_UNROLL used BN_LLONG mode RC4_INDEX mode RC4_CHUNK is undefined Makefile = Makefile.ssl e_os.h = include/openssl/e_os.h [File exists] e_os2.h = include/openssl/e_os2.h [File exists] making links in crypto... make[1]: Entering directory `/work/icccode/openssl-0.9.6c/crypto' Makefile = Makefile.ssl crypto.h = ../include/openssl/crypto.h [File exists] tmdiff.h = ../include/openssl/tmdiff.h [File exists] opensslv.h = ../include/openssl/opensslv.h [File exists] opensslconf.h = ../include/openssl/opensslconf.h [File exists] ebcdic.h = ../include/openssl/ebcdic.h [File exists] symhacks.h = ../include/openssl/symhacks.h [File exists] Makefile = Makefile.ssl making links in crypto/md2... make[2]: Entering directory `/work/icccode/openssl-0.9.6c/crypto/md2' Makefile = Makefile.ssl md2.h = ../../include/openssl/md2.h [File exists] md2test.c = ../../test/md2test.c [File exists] make[2]: Leaving directory `/work/icccode/openssl-0.9.6c/crypto/md2' making links in crypto/md4... make[2]: Entering directory `/work/icccode/openssl-0.9.6c/crypto/md4' Makefile = Makefile.ssl md4.h = ../../include/openssl/md4.h [File exists] md4test.c = ../../test/md4test.c [File exists] md4.c = ../../apps/md4.c [File exists] make[2]: Leaving directory `/work/icccode/openssl-0.9.6c/crypto/md4' making links in crypto/md5... make[2]: Entering directory `/work/icccode/openssl-0.9.6c/crypto/md5' Makefile = Makefile.ssl md5.h = ../../include/openssl/md5.h [File exists] md5test.c = ../../test/md5test.c [File exists] make[2]: Leaving directory `/work/icccode/openssl-0.9.6c/crypto/md5' making links in crypto/sha... make[2]: Entering directory `/work/icccode/openssl-0.9.6c/crypto/sha' Makefile = Makefile.ssl sha.h = ../../include/openssl/sha.h [File exists] shatest.c = ../../test/shatest.c [File exists] sha1test.c = ../../test/sha1test.c [File exists] make[2]: Leaving directory `/work/icccode/openssl-0.9.6c/crypto/sha' making links in crypto/mdc2... make[2]: Entering directory `/work/icccode/openssl-0.9.6c/crypto/mdc2' Makefile = Makefile.ssl mdc2.h = ../../include/openssl/mdc2.h [File exists] mdc2test.c = ../../test/mdc2test.c [File exists] make[2]: Leaving directory `/work/icccode/openssl-0.9.6c/crypto/mdc2' making links in crypto/hmac... make[2]: Entering directory `/work/icccode/openssl-0.9.6c/crypto/hmac' Makefile = Makefile.ssl hmac.h = ../../include/openssl/hmac.h [File exists] hmactest.c = ../../test/hmactest.c [File exists] make[2]: Leaving directory `/work/icccode/openssl-0.9.6c/crypto/hmac' making links in crypto/ripemd... make[2]: Entering directory `/work/icccode/openssl-0.9.6c/crypto/ripemd' Makefile = Makefile.ssl ripemd.h = ../../include/openssl/ripemd.h [File exists] rmdtest.c = ../../test/rmdtest.c [File exists] make[2]: Leaving directory `/work/icccode/openssl-0.9.6c/crypto/ripemd' making links in crypto/des... make[2]: Entering directory `/work/icccode/openssl-0.9.6c/crypto/des' Makefile = Makefile.ssl asm/perlasm = ../../perlasm des.h = ../../include/openssl/des.h [File exists] destest.c = ../../test/destest.c [File exists] make[2]: Leaving directory `/work/icccode/openssl-0.9.6c/crypto/des' making links in crypto/rc2... make[2]: Entering directory `/work/icccode/openssl-0.9.6c/crypto/rc2' Makefile = Makefile.ssl rc2.h = ../../include/openssl/rc2.h [File exists] rc2test.c = ../../test/rc2test.c [File exists] make[2]: Leaving directory `/work/icccode/openssl-0.9.6c/crypto/rc2' making links in crypto/rc4... make[2]: Entering directory `/work/icccode/openssl-0.9.6c/crypto/rc4' Makefile = Makefile.ssl rc4.h = ../../include/openssl/rc4.h [File exists] rc4test.c = ../../test/rc4test.c [File exists] make[2]: Leaving directory `/work/icccode/openssl-0.9.6c/crypto/rc4' making links in crypto/rc5... make[2]: Entering directory
Re: [openssl.org #26] 64 bit Suse Linux on PowerPC
On Thu, 9 May 2002, John Bihlmeyer via RT wrote: Hello to all, I am trying to compile on a 64 bit Suse sles7 powerpc system. the error message indicates -m486 is an invalid compiler parameter. Anyone know the parameters I need to give ./config to get it to work for 64 bit Suse on a powerpc below are the results from running ./config without parameters and the results from running the make command. Thanks for all your help John running ./config gave me the following::: Operating system: ppc64-whatever-linux2 Configuring for linux-elf Configuring for linux-elf ^ That will not work for you. Try ./Configure linux-ppc -- Tim RiceMultitalents(707) 887-1469 [EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
[openssl.org #26] 64 bit Suse Linux on PowerPC
[[EMAIL PROTECTED] - Thu May 9 22:13:32 2002]: I am trying to compile on a 64 bit Suse sles7 powerpc system. the error message indicates -m486 is an invalid compiler parameter. Anyone know the parameters I need to give ./config to get it to work for 64 bit Suse on a powerpc below are the results from running ./config without parameters and the results from running the make command. Operating system: ppc64-whatever-linux2 Configuring for linux-elf Obviously config mistakenly selects the linux-elf target that is used for x86 platforms. (This is a bug that has to be fixed.) Configure also contains an entry for linux-ppc, I however don't know whether it is suitable for 64bit PowerPC. Please try Configure linux-ppc directly instead of calling config and keep us updated, whether it works out. Best regards, Lutz __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
