Re: HPUX compile woes

2006-01-26 Thread Rick Jones

Jeff Fulmer wrote:

On Thu, Jan 26, 2006 at 12:58:21PM -0800, Rick Jones wrote:


Second, _which_ gcc version?



Reading specs from
/opt/gcc/lib/gcc-lib/hppa2.0n-hp-hpux11.00/2.95.2/specs
gcc version 2.95.2 19991024 (release)


Are you still running 11.0?




Yeah, B.11.00 


Tick tock...   bummer you aren't on a later OS, you could grab the OpenSSL from 
HP's Internet Express bits.  Or if having the HP compiler would have helped you 
could have used one of the systems at www.testdrive.hp.com (guessing).


Do other things compile cleanly with the ancient gcc?  _Is_ there any chance of 
using the HP ANSI C compiler if for no other reason than to be a sanity check? 
I suppose trying to get a later gcc might be another interesting excercise.


rick
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   [EMAIL PROTECTED]


Re: HPUX compile woes

2006-01-26 Thread Jeff Fulmer
On Thu, Jan 26, 2006 at 12:58:21PM -0800, Rick Jones wrote:
> >>Second, _which_ gcc version?
> >
> >
> >Reading specs from
> >/opt/gcc/lib/gcc-lib/hppa2.0n-hp-hpux11.00/2.95.2/specs
> >gcc version 2.95.2 19991024 (release)
> 
> Are you still running 11.0?
> 

Yeah, B.11.00 

-- 
#include 
int main(){int a[]={74,117,115,116,32,97,110,111,116,104,101,114,32, \
67,32,104,97,99,107,101,114,10,0}; int *b=a;while(*b>0)putchar(*b++);}
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   [EMAIL PROTECTED]


Re: HPUX compile woes

2006-01-26 Thread Rick Jones

Second, _which_ gcc version?



Reading specs from
/opt/gcc/lib/gcc-lib/hppa2.0n-hp-hpux11.00/2.95.2/specs
gcc version 2.95.2 19991024 (release)


Are you still running 11.0?

rick jones
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   [EMAIL PROTECTED]


Re: HPUX compile woes

2006-01-26 Thread Jeff Fulmer
On Thu, Jan 26, 2006 at 12:08:36PM -0800, Rick Jones wrote:
> Jeff Fulmer wrote:
> >I'm trying to compile openssl-0.9.8a on HPUX with the following
> >configuration:
> >
> >#!/bin/sh
> > 
> >./config \
> >  --prefix=/usr/local/ssl \
> >  no-asm   \
> >  threads   \
> >  zlib   \
> >  -fPIC 
> >
> >It barfs here everytime. I wouldn't think it would go to the assembler
> >with the no-asm: 
> >
> >gcc -I.. -I../.. -I../../include -DZLIB -DOPENSSL_THREADS  -DDSO_DL
> >-fPIC -D_REENTRANT -march=2.0 -O3 -DB_ENDIAN -D_REENTRANT   -c -o
> >b_print.o b_print.c
> >/var/tmp/cc8MBUWc.s: Assembler messages:
> >/var/tmp/cc8MBUWc.s:1242: Error: Unknown opcode: `fneg'
> >make[2]: *** [b_print.o] Error 1
> >make[2]: Leaving directory
> >`/home/jdfulmer/src/openssl-0.9.8a/crypto/bio'
> >make[1]: *** [subdirs] Error 1
> >make[1]: Leaving directory `/home/jdfulmer/src/openssl-0.9.8a/crypto'
> >make: *** [build_crypto] Error 1
> >
> >Any thoughts?
> 
> First thought, _which_ HPUX revision and platform (PA or IPF)? (I'm 
> guessing PA since it says -march=2.0 but who knows... :)

Correct: PA

> 
> Second, _which_ gcc version?

Reading specs from
/opt/gcc/lib/gcc-lib/hppa2.0n-hp-hpux11.00/2.95.2/specs
gcc version 2.95.2 19991024 (release)
 
> Third, is the /var/tmp/cc8MBUWc.s file an assembly file from openssl, or is 
> it perhaps an assembly file from the compiler and there is a mismatch 
> bewteen the front-end and the back-end?  Is gcc using the gnu (?) assembler 
> or the HP assembler?  I've no idea which it should use, but do recall there 
> being issues in that area in the past in other places.

I believe I'm using the gnu assembler; not sure if it agrees...
 
> Fourth - any particular reason you are tossing-out any of the previous good 
> work done for fast assembly versions of some things?
 
Largely because the the last time I compiled openssl on HPUX after much
blood, sweat and tears my success was found by turing off the assembler.
If I could utilize all that good work, I'd love to...


> BTW, that reminds me of something I've been meaning to ask - does the 
> --no-asm simply preclude using stuff in a -s file, or will it also disable 
> the use of assembly that is inline in a .c file?  I seem to recall that 
> some of the hand-crafted assembly routines for some platforms are in .c 
> files rather than .s files.
> __
> OpenSSL Project http://www.openssl.org
> User Support Mailing Listopenssl-users@openssl.org
> Automated List Manager   [EMAIL PROTECTED]
> 

Jeff

-- 
#include 
int main(){int a[]={74,117,115,116,32,97,110,111,116,104,101,114,32, \
67,32,104,97,99,107,101,114,10,0}; int *b=a;while(*b>0)putchar(*b++);}
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   [EMAIL PROTECTED]


Re: HPUX compile woes

2006-01-26 Thread Rick Jones

Jeff Fulmer wrote:

I'm trying to compile openssl-0.9.8a on HPUX with the following
configuration:

#!/bin/sh
 
./config \

  --prefix=/usr/local/ssl \
  no-asm   \
  threads   \
  zlib   \
  -fPIC 


It barfs here everytime. I wouldn't think it would go to the assembler
with the no-asm: 


gcc -I.. -I../.. -I../../include -DZLIB -DOPENSSL_THREADS  -DDSO_DL
-fPIC -D_REENTRANT -march=2.0 -O3 -DB_ENDIAN -D_REENTRANT   -c -o
b_print.o b_print.c
/var/tmp/cc8MBUWc.s: Assembler messages:
/var/tmp/cc8MBUWc.s:1242: Error: Unknown opcode: `fneg'
make[2]: *** [b_print.o] Error 1
make[2]: Leaving directory
`/home/jdfulmer/src/openssl-0.9.8a/crypto/bio'
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory `/home/jdfulmer/src/openssl-0.9.8a/crypto'
make: *** [build_crypto] Error 1


Any thoughts?


First thought, _which_ HPUX revision and platform (PA or IPF)? (I'm guessing PA 
since it says -march=2.0 but who knows... :)


Second, _which_ gcc version?

Third, is the /var/tmp/cc8MBUWc.s file an assembly file from openssl, or is it 
perhaps an assembly file from the compiler and there is a mismatch bewteen the 
front-end and the back-end?  Is gcc using the gnu (?) assembler or the HP 
assembler?  I've no idea which it should use, but do recall there being issues 
in that area in the past in other places.


Fourth - any particular reason you are tossing-out any of the previous good work 
done for fast assembly versions of some things?


rick jones

BTW, that reminds me of something I've been meaning to ask - does the --no-asm 
simply preclude using stuff in a -s file, or will it also disable the use of 
assembly that is inline in a .c file?  I seem to recall that some of the 
hand-crafted assembly routines for some platforms are in .c files rather than .s 
files.

__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   [EMAIL PROTECTED]


HPUX compile woes

2006-01-26 Thread Jeff Fulmer
I'm trying to compile openssl-0.9.8a on HPUX with the following
configuration:

#!/bin/sh
 
./config \
  --prefix=/usr/local/ssl \
  no-asm   \
  threads   \
  zlib   \
  -fPIC 

It barfs here everytime. I wouldn't think it would go to the assembler
with the no-asm: 

gcc -I.. -I../.. -I../../include -DZLIB -DOPENSSL_THREADS  -DDSO_DL
-fPIC -D_REENTRANT -march=2.0 -O3 -DB_ENDIAN -D_REENTRANT   -c -o
b_print.o b_print.c
/var/tmp/cc8MBUWc.s: Assembler messages:
/var/tmp/cc8MBUWc.s:1242: Error: Unknown opcode: `fneg'
make[2]: *** [b_print.o] Error 1
make[2]: Leaving directory
`/home/jdfulmer/src/openssl-0.9.8a/crypto/bio'
make[1]: *** [subdirs] Error 1
make[1]: Leaving directory `/home/jdfulmer/src/openssl-0.9.8a/crypto'
make: *** [build_crypto] Error 1

Any thoughts?

Cheers,
Jeff

-- 
#include 
int main(){int a[]={74,117,115,116,32,97,110,111,116,104,101,114,32, \
67,32,104,97,99,107,101,114,10,0}; int *b=a;while(*b>0)putchar(*b++);}
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager   [EMAIL PROTECTED]