Upgrading from 4.0-RELEASE broken
I always get bitten by these bugs while trying to upgrade a 4.0-RELEASE
box to 5.0-CURRENT via make world:
Problem #1:
=== libcrypto
perl
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/objects/obj_dat.
pl
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/objects/objects.
h /usr/obj/usr/src/secure/lib/libcrypto/obj_dat.h
Can't open input file at
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/cr
ypto/objects/obj_dat.pl line 41.
*** Error code 2
Stop in /usr/src/secure/lib/libcrypto.
*** Error code 1
Fix #1:
+++ obj_dat.pl.bak Sun Jun 11 16:56:31 2000
--- obj_dat.pl Sun Jun 11 16:56:52 2000
@@ -38,8 +38,8 @@
return(%objn);
}
-open (IN,"$ARGV[0]") || die "Can't open input file $ARGV[0]";
-open (OUT,"$ARGV[1]") || die "Can't open output file $ARGV[1]";
+#open (IN,"$ARGV[0]") || die "Can't open input file $ARGV[0]";
+#open (OUT,"$ARGV[1]") || die "Can't open output file $ARGV[1]";
while (IN)
{
Problem #2:
cc -O -pipe -Wall -DHAVE_DES -I/usr/obj/usr/src/i386/usr/include -c
/usr/src/usr
.sbin/ppp/ether.c
cc -O -pipe -Wall -DHAVE_DES -I/usr/obj/usr/src/i386/usr/include -o
ppp acf.o a
rp.o async.o auth.o bundle.o cbcp.o ccp.o chap.o chat.o command.o
datalink.o defla
te.o defs.o exec.o filter.o fsm.o hdlc.o id.o iface.o ip.o ipcp.o
iplist.o lcp.o l
ink.o log.o lqr.o main.o mbuf.o mp.o pap.o physical.o pred.o probe.o
prompt.o prot
o.o route.o server.o sig.o slcompress.o sync.o systems.o tcp.o
throughput.o timer.
o tty.o tun.o udp.o vjcomp.o nat_cmd.o chap_ms.o radius.o i4b.o ether.o
-lcrypt -
lmd -lutil -lz -lalias -lcrypto -lradius -lnetgraph
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509at_get_att
r_by_OBJ'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509_CERT_AUX_
free'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`OpenSSL_add_al
l_ciphers'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`d2i_X509_CERT_
AUX'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`BN_CTX_new'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509at_add1_at
tr_by_txt'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`BN_CTX_get'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509_CERT_AUX_
print'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`BN_CTX_end'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509at_add1_at
tr_by_NID'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`BN_CTX_start'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`BN_CTX_init'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509_PURPOSE_g
et0'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`OpenSSL_add_al
l_digests'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`i2d_X509_CERT_
AUX'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509at_get_att
r'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509at_get_att
r_count'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`v3_info'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509_TRUST_get
_by_id'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509_PURPOSE_g
et_by_id'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509_check_tru
st'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509at_delete_
attr'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`BN_CTX_free'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`ERR_load_RAND_
strings'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509at_add1_at
tr'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`ASN1_STRING_se
t_by_NID'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509at_get_att
r_by_NID'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509at_add1_at
tr_by_OBJ'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`X509_check_pur
pose'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`CRYPTO_mem_ctr
l'
/usr/obj/usr/src/i386/usr/lib/libcrypto.so: undefined reference to
`DSA_OpenSSL'
*** Error code 1
Stop in /usr/src/usr.sbin/ppp.
*** Error code 1
Fix #2:
No idea how to fix this...
--
Andre
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Upgrading to 4.0
after seeing your steps.. it makes sense pre-build the kernel to 4.0 _before_ installing world. however... could you provide a little more info on steps 5, 6, 7 specifically.. what does the -DNOINFO do ( i can't find it on my system.. yet) -DNOINFO is documented in src/Makefile.inc1, it is required for successful -current installworld from 3.x due to bootstrapping problems (-current install-info(1) has two new options). AHAA !! those new options wouldn't by any chance be --section --entry ??? i got an error on my original make saying --defsection --defentry were invalid options after man'ing "install-info" i went into /usr/share/src/mk and edited bsd.info.mk appropriately. however... THAT didn't work.. someone suggested doing a "make install" in /usr/share/src/mk of course, that didn't work either guess i'm just saying that this all makes a lot more sense now... thanks for all the help on all this gonna give it a shot right now in fact :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrading to 4.0
[Redirected to -current] On Wed, Feb 09, 2000 at 11:49:30AM -0800, Cy Schubert wrote: Can FreeBSD be upgraded from 3.4-stable to 4.0-current from source. When I installed -current on my testbed I got a number of sig 12's (SIGSYS), e.g. fix one, reiterate, fix the next one, etc., that I finally gave up and installed 4.0-current from snapshot. The reason for asking is that I'm installing a console server in Vancouver, a 30 minute flight by helijet from Victoria. My options are to install -stable and subsequently install 4.1 from source, negating the requirement to travel to Vancouver to perform the installation, or install from CDROM or FTP requiring console access. Any thoughts? Without providing any in-depth details: 0. `uname -r' returns 3.x 1. make buildworld 2. make buildkernel 3. make installkernel 4. reboot with new kernel in signle-user mode 5. make -DNOINFO installworld 6. make buildkernel installkernel (again) 7. make installworld (again, without -DNOINFO) -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrading to 4.0
In message [EMAIL PROTECTED], Ruslan Ermilov writes: [Redirected to -current] On Wed, Feb 09, 2000 at 11:49:30AM -0800, Cy Schubert wrote: Can FreeBSD be upgraded from 3.4-stable to 4.0-current from source. When I installed -current on my testbed I got a number of sig 12's (SIGSYS), e.g. fix one, reiterate, fix the next one, etc., that I finally gave up and installed 4.0-current from snapshot. The reason for asking is that I'm installing a console server in Vancouver, a 30 minute flight by helijet from Victoria. My options are to install -stable and subsequently install 4.1 from source, negating the requirement to travel to Vancouver to perform the installation, or install from CDROM or FTP requiring console access. Any thoughts? Without providing any in-depth details: 0. `uname -r' returns 3.x 1. make buildworld 2. make buildkernel 3. make installkernel 4. reboot with new kernel in signle-user mode 5. make -DNOINFO installworld 6. make buildkernel installkernel (again) 7. make installworld (again, without -DNOINFO) Excellent. I'll try it on my testbed and let you know how it goes. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX GroupInternet: [EMAIL PROTECTED] ITSD Province of BC "COBOL IS A WASTE OF CARDS." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrading to 4.0
On Wed, Feb 09, 2000 at 04:36:07PM -0600, nathan wrote: I've also had problems upgrading from 3.4-RELEASE to 4.0 i have a dual proc system, and have been EAGERLY anticipating 4.0 so i can install WINE, VMWARE, etc my process went like this 1. boot normally 2. killall -TERM inetd 3. cd /usr/src 4. make -j8 -DNOPROFILE=true buildworld 5. make -j8 -DNOPROFILE=true installworld step 4 completed no problem... step 5, however, always failed... THEN, i had the long, undesirable task of restoring my system back to 3.4 ... later.. i tried rebooting to single mode to do step 5.. but again.. it failed. after seeing your steps.. it makes sense pre-build the kernel to 4.0 _before_ installing world. however... could you provide a little more info on steps 5, 6, 7 specifically.. what does the -DNOINFO do ( i can't find it on my system.. yet) -DNOINFO is documented in src/Makefile.inc1, it is required for successful -current installworld from 3.x due to bootstrapping problems (-current install-info(1) has two new options). and why repeat the kernel build/install AND the installworld?? Hmm, just to be 100% sure. I would also recommend buildworld/ installworld right after 3.x-4.0 upgrade. But it is really not required, since `buildkernel' builds the -current kernel with the -current (latest) compiler. also... if this should work... i wonder why the fbsd Handbook (www.freebsd.org/handbook/makeworld.html) details a very different process than this one. Because this process is a complex transition step, while handbook describes the usual X.Y-RELEASE - X.Y-STABLE case. Note, that ir also does not say anything about aout-elf transition. lastly.. are your steps 2 3 the same as cd /sys/i386/conf vi CONFIG_FILE cd ../../compile/CONFIG_FILE make depend make make install Nope. There are special `buildkernel', `installkernel' targets in the src/Makefile.inc1. They are different from the procedure above in that they compile the -current kernel with the -current compiler, built in a host environment (i.e. with 4.0 gcc from /usr/src built on 3.x). ??? thanks for ANY additional info you can provide... i've spent a week reading/compiling/reading/testing/crashing/etc etc etc Without providing any in-depth details: 0. `uname -r' returns 3.x 1. make buildworld 2. make buildkernel 3. make installkernel 4. reboot with new kernel in signle-user mode 5. make -DNOINFO installworld 6. make buildkernel installkernel (again) 7. make installworld (again, without -DNOINFO) -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
