Re: HP-UX Poblem

2006-04-20 Thread [EMAIL PROTECTED]
Hi, > I've just tried compiling OpenSSL-0.9.8a for HPPA64 architecture > (using gcc-4.1) and 'make test' ends with > > > ... > > ecb idea ok > > cbc idea ok > > cfb64 idea ok > > ../util/shlib_wrap.sh ./shatest > > *** Termination signal 139 > > > > Stop. > > *** Error exit co

Re: HP-UX Poblem

2006-04-20 Thread Rick Jones
[EMAIL PROTECTED] wrote: Hi, I've just tried compiling OpenSSL-0.9.8a for HPPA64 architecture (using gcc-4.1) and 'make test' ends with ... ecb idea ok cbc idea ok cfb64 idea ok ../util/shlib_wrap.sh ./shatest *** Termination signal 139 Stop. *** Error exit code 1 Stop.

Re: HP-UX Poblem

2006-04-21 Thread Stefan . Neis
Hi, > > > >>I've just tried compiling OpenSSL-0.9.8a for HPPA64 architecture > >>(using gcc-4.1) and 'make test' ends with > >> > >> > >>>... > >>>ecb idea ok > >>>cbc idea ok > >>>cfb64 idea ok > >>>../util/shlib_wrap.sh ./shatest > >>>*** Termination signal 139 > >>> > >>>Stop

Re: HP-UX Poblem

2006-04-21 Thread Rick Jones
Has using a different compiler been suggested already? Any suggestions for the newest gcc that's known to work? 3.4.5? I'm using one of HP's "Testdrive" machines for building, so I suppose building several compilers wouldn't be appreciated too much, especially since the 4.1.0 that's causing

Re: HP-UX Poblem

2006-04-21 Thread Stefan . Neis
Hi, > Since you are on an HP testdrive system, why not try the HP compilers? Yes, right. In the end I try to port some C++ code that's only ever been compiled with gcc, so I don't really want to either fix the "bugs" that gcc tolerates nor add workarounds for the correct code that HP's co

Re: HP-UX Poblem

2006-04-21 Thread Rick Jones
[EMAIL PROTECTED] wrote: Hi, Since you are on an HP testdrive system, why not try the HP compilers? Yes, right. In the end I try to port some C++ code that's only ever been compiled with gcc, so I don't really want to either fix the "bugs" that gcc tolerates nor add workarounds f

Re: HP-UX Poblem

2006-04-21 Thread Stefan . Neis
Hi, > > so I didn't really think of using HP's compiler. Well, using HP's compiler, I get an OpenSSL version which does successfully pass the "make test" command... Looks more and more like a bug in gcc-4.1 > Portable code is a chore ain't it :) It could be worse, you could be > trying t