Try this:

Update ports, src, sys, and XF4 archives to -stable as outlined on
http://www.openbsd.org/anoncvs.html.  After you've got -stable ports and
source, re-compile your kernel and your userland as outlined on
http://www.openbsd.org/stable.html.

Then, while your userland binaries are recompiling (it takes quite a
while), read the relevant FAQ entries starting at
http://www.openbsd.org/faq/index.html.  They're wonderful documents,
most of your questions can be answered by reading them.

Federico Giannici wrote:
> z0mbix wrote:
>> On 11/11/06, Federico Giannici <[EMAIL PROTECTED]> wrote:
>>> Dunceor wrote:
>>> > On 11/11/06, *Federico Giannici* <[EMAIL PROTECTED]
>>> > <mailto:[EMAIL PROTECTED]>> wrote:
>>> >
>>> >     I have upgraded an amd64 from 3.9 to 4.0.
>>> >     I followed all the Upgrade Guide using install media.
>>> >     Updated packages.
>>> >     Updated sys sources to -stable and made a new kernel.
>>> >     Everything worked perfectly.
>>> >
>>> >     Then I download and extracted " src.tar.gz". Nothing else was
>>> present in
>>> >     the "src" directory but "sys".
>>> >
>>> >     I applied the "002_openssl.patch" patch and all hunks succeeded.
>>> >     Followed all compile instructions (included the "make
>>> includes"), but
>>> >     the "make" interrupts with the following errors:
>>> >
>>> >     cc -O2 -pipe -g -DL_ENDIAN -DDSO_DLFCN -DHAVE_DLFCN_H
>>> -DOPENSSL_NO_IDEA
>>> >     -DTERMIOS -DANSI_SOURCE -DNO_ERR -DOPENSSL_NO_ASM -DOPENSSL_NO_RC5
>>> >     -DOPENSSL_NO_KRB5 -DOPENSSL_NO_MDC2 -DNO_WINDOWS_BRAINDEATH
>>> >     -DOPENSSL_NO_HW_CSWIFT -DOPENSSL_NO_HW_NCIPHER
>>> -DOPENSSL_NO_HW_ATALLA
>>> >     -DOPENSSL_NO_HW_NURON -DOPENSSL_NO_HW_UBSEC -DOPENSSL_NO_HW_AEP
>>> >     -DOPENSSL_NO_HW_SUREWARE -DOPENSSL_NO_HW_4758_CCA
>>> >     -I/usr/src/lib/libssl/crypto/../src
>>> >     -I/usr/src/lib/libssl/crypto/../src/crypto
>>> >     -I/usr/src/lib/libssl/crypto/obj   -c
>>> >     /usr/src/lib/libssl/src/crypto/rsa/rsa_x931.c -o rsa_x931.o
>>> >     /usr/src/lib/libssl/src/crypto/rsa/rsa_x931.c: In function
>>> >     `RSA_X931_hash_id':
>>> >     /usr/src/lib/libssl/src/crypto/rsa/rsa_x931.c:165: error:
>>> `NID_sha256'
>>> >     undeclared (first use in this function)
>>> >     /usr/src/lib/libssl/src/crypto/rsa/rsa_x931.c:165: error: (Each
>>> >     undeclared identifier is reported only once
>>> >     /usr/src/lib/libssl/src/crypto/rsa/rsa_x931.c:165: error: for each
>>> >     function it appears in.)
>>> >     /usr/src/lib/libssl/src/crypto/rsa/rsa_x931.c:168: error:
>>> `NID_sha384'
>>> >     undeclared (first use in this function)
>>> >     /usr/src/lib/libssl/src/crypto/rsa/rsa_x931.c:171: error:
>>> `NID_sha512'
>>> >     undeclared (first use in this function)
>>> >     *** Error code 1
>>> >
>>> >     Stop in /usr/src/lib/libssl/crypto.
>>> >     *** Error code 1
>>> >
>>> >     Stop in /usr/src/lib/libssl.
>>> >
>>> >
>>> >     What could be the problem?
>>> >
>>> >     Thanks.
>>
>> Why are you trying to patch if you've upgraded to -stable? Do one of
>> the other. Go and re-read the FAQ about the differences between
>> running release + patches, stable and current.
> 
> I have written that I upgraded to -stable the KERNEL (src/sys) and
> compiled a new one.
> 
> THEN I extracted the src.tar.gz archive, patched it with
> "002_openssl.patch", and note that the patch SUCCEDED.
> 
> Then I tried to compile the library (following instruction in the head
> of the patch) and, after a while, the compilation aborted.
> 
> 
> Bye.
> 


-- 
Joel Goguen
Bachelor of Computer Science III
University of New Brunswick
http://iapetus.dyndns.org/

Reply via email to