Hi,


Many thanks for your quick response. The fix worked. This ticket can be closed 
then.



Just a few another questions: 

1. Do you know when next release becomes available?

2. Do you continue maintaining both 0.9.x stream and 1.0.x, or will openSSL 
move at a certain point to 1.x only? It is a little bit confusing that two 
releases are maintained, not sure which of them to choose. It may be useful to 
put some words in the FAQ (http://www.openssl.org/support/faq.html) regarding 
0.9x and 1.0x versions?



Regards,

Kees



-----Original Message-----

From: Andy Polyakov via RT [mailto:[email protected]] 

Sent: Thursday, 22 July, 2010 10:07

To: Kees Dekker

Cc: [email protected]

Subject: Re: [openssl.org #2309] build of openssl1.0.0a failed on Tru64 5.1b: 
No rule to make target `alphacpuid.o'



Hi,



> When building openSSL on Tru64, 5.1b-3, I get:

>  

> $ gmake

> making all in crypto...

> gmake[1]: Entering directory 
> `/home/port/MaintASM.night.rel/thirdparty/OpenSSL/32bit/openssl-1.0.0a/crypto'

> gmake[1]: *** No rule to make target `alphacpuid.o', needed by 
> `../libcrypto.a'.  Stop.

> gmake[1]: Leaving directory 
> `/home/port/MaintASM.night.rel/thirdparty/OpenSSL/32bit/openssl-1.0.0a/crypto'

> gmake: *** [build_crypto] Error 1

>  

> I did not find any source file named *alphacpuid*. The Configure file

> tells something about a perl variable $alpha_asm. May be something got

> lost in the crypto directory,



Yes. Apparently it's a packaging issue in the sense that relevant file

was erroneously omitted from released tar-ball. It will have to be

addressed in next release. Meanwhile you'll have to fetch the missing

file, alphacpuid.s, at following location:



http://cvs.openssl.org/getfile?f=openssl/crypto/alphacpuid.s&v=1.3



As URL suggests it should be places to ./crypto directory. A.





______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [email protected]

Reply via email to