Re: Problem Building World
Cyber Dog wrote: Hello, I'm working with a server currently running FreeBSD 4.6. Clearly it hasn't been updated too recently, and I've made it my goal to bring it into the present. This would be my first time rebuilding a FreeBSD OS. I started out by clearing out /usr/src, and doing a fresh cvsup with the following supfile: snip *default release=cvs tag=RELENG_4_10 *default delete use-rel-suffix # If your network link is a T1 or faster, comment out the following line. *default compress ## Main Source Tree. # # The easiest way to get the main source tree is to use the src-all # mega-collection. It includes all of the individual src-* collections. # Please note: If you want to track -STABLE, leave this uncommented. src-all ports-all tag=. As far as I can tell, all went well with that. I've been using the documentation at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I cleared out /usr/obj as it describes. Then I cd /usr/src, and do a make buildworld. It churns along for awhile, but then we hit the problem area: === secure/lib/libcrypto ( echo #ifndef MK1MF_BUILD; echo /* auto-generated by crypto/Makefile.ssl for crypto/cversion.c */; echo #define CFLAGS \cc\; echo #define PLATFORM \`uname -s`-`uname -m`\; echo #define DATE \`LC_ALL=C date`\; echo #endif ) buildinf.h rm -f .depend mkdep -f .depend -a-I/usr/local/include -I/usr/local/lib -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine -I/usr/obj/usr/src/secure/lib/libcrypto -DL_ENDIAN [large snip of build output] /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/x509v3/v3_utl.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/x509v3/v3err.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cryptlib.c:109: #error Inconsistency between crypto.h and cryptlib.c mkdep: compile failed *** Error code 1 Stop in /usr/src/secure/lib/libcrypto. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. [EMAIL PROTECTED] src]# As you can see, something's amiss here. I don't understand why there would be any inconsistencies...as I said; I did a fresh CVSup (multiple times in fact). Any help would be greatly appreciated! - Matt Hi, Matt: I'm certainly not an expert here, but it seems like it's an awful long way from 4.6 to 4.10. Have you tried an intermediate update, say, 4.6 to 4.7 [or 4.8]? So many changes occur over time; and by the time 4.10 came out, 4.6 was very old*; so it's entirely possible that you might need to do a cvsup/buildworld routine to something a little closer to your box's date prior to attempting (and having any success) with 4.10. You might try changing the 'cvs tag' in your supfile to RELENG_4_7 or RELENG_4_8 and going again Kevin Kinsey *and probably past it's EOL. Whether or not, I'm sure it'd be nice if it _would_ build, but it's possible that the engineering team was under no compunction to test a migration from 4.6 directly to 4.10 at the time 4.10 was being tested for release, and therefore it wasn't (tested) ... like I said, I'm no expert, but a 'stepping stone' approach to the problem might work ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem Building World
On Mon, 15 Nov 2004, Kevin D. Kinsey, DaleCo, S.P. wrote: Cyber Dog wrote: Hello, I'm working with a server currently running FreeBSD 4.6. Clearly it hasn't been updated too recently, and I've made it my goal to bring it into the present. This would be my first time rebuilding a FreeBSD OS. I started out by clearing out /usr/src, and doing a fresh cvsup with the following supfile: snip [more snip] Stop in /usr/src. [EMAIL PROTECTED] src]# As you can see, something's amiss here. I don't understand why there would be any inconsistencies...as I said; I did a fresh CVSup (multiple times in fact). Any help would be greatly appreciated! - Matt Hi, Matt: I'm certainly not an expert here, but it seems like it's an awful long way from 4.6 to 4.10. Have you tried an intermediate update, say, 4.6 to 4.7 [or 4.8]? So many changes occur over time; and by the time 4.10 came out, 4.6 was very old*; so it's entirely possible that you might need to do a cvsup/buildworld routine to something a little closer to your box's date prior to attempting (and having any success) with 4.10. You might try changing the 'cvs tag' in your supfile to RELENG_4_7 or RELENG_4_8 and going again Kevin Kinsey *and probably past it's EOL. Whether or not, I'm sure it'd be nice if it _would_ build, but it's possible that the engineering team was under no compunction to test a migration from 4.6 directly to 4.10 at the time 4.10 was being tested for release, and therefore it wasn't (tested) ... like I said, I'm no expert, but a 'stepping stone' approach to the problem might work I did this exact upgrade (4.6 to 4.10) a while back, and I can endorse the 'stepping stone' procedure. I did a cvsup and rebuild from 4.6 to 4.7, 4.7 to 4.8, etc. until 4.10. It's tedious and time-consuming, but the whole thing went surprisingly smoothly. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging | ] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem Building World
On Mon, Nov 15, 2004 at 06:49:22PM -0500, Chris Hill wrote: I did this exact upgrade (4.6 to 4.10) a while back, and I can endorse the 'stepping stone' procedure. I did a cvsup and rebuild from 4.6 to 4.7, 4.7 to 4.8, etc. until 4.10. It's tedious and time-consuming, but the whole thing went surprisingly smoothly. If you have access to the console, you can just avoid the hassle and do a binary upgrade from installation media. Kris pgpe1nS1mTJ5E.pgp Description: PGP signature
RE: Problem Building World
-Original Message- From: Chris Hill [mailto:[EMAIL PROTECTED] Sent: Monday, November 15, 2004 6:49 PM To: Kevin D. Kinsey, DaleCo, S.P. Cc: Cyber Dog; [EMAIL PROTECTED] Subject: Re: Problem Building World On Mon, 15 Nov 2004, Kevin D. Kinsey, DaleCo, S.P. wrote: Cyber Dog wrote: Hello, I'm working with a server currently running FreeBSD 4.6. Clearly it hasn't been updated too recently, and I've made it my goal to bring it into the present. This would be my first time rebuilding a FreeBSD OS. I started out by clearing out /usr/src, and doing a fresh cvsup with the following supfile: snip [more snip] Stop in /usr/src. [EMAIL PROTECTED] src]# As you can see, something's amiss here. I don't understand why there would be any inconsistencies...as I said; I did a fresh CVSup (multiple times in fact). Any help would be greatly appreciated! - Matt Hi, Matt: I'm certainly not an expert here, but it seems like it's an awful long way from 4.6 to 4.10. Have you tried an intermediate update, say, 4.6 to 4.7 [or 4.8]? So many changes occur over time; and by the time 4.10 came out, 4.6 was very old*; so it's entirely possible that you might need to do a cvsup/buildworld routine to something a little closer to your box's date prior to attempting (and having any success) with 4.10. You might try changing the 'cvs tag' in your supfile to RELENG_4_7 or RELENG_4_8 and going again Kevin Kinsey *and probably past it's EOL. Whether or not, I'm sure it'd be nice if it _would_ build, but it's possible that the engineering team was under no compunction to test a migration from 4.6 directly to 4.10 at the time 4.10 was being tested for release, and therefore it wasn't (tested) ... like I said, I'm no expert, but a 'stepping stone' approach to the problem might work I did this exact upgrade (4.6 to 4.10) a while back, and I can endorse the 'stepping stone' procedure. I did a cvsup and rebuild from 4.6 to 4.7, 4.7 to 4.8, etc. until 4.10. It's tedious and time-consuming, but the whole thing went surprisingly smoothly. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging | ] I typo'd my original email, I'm starting with FreeBSD 4.7, not 6. Regardless, your suggestion made sense of stepping stoning the procedure... unfortunately I got the exact same results. I CVSup'd 4.6, cleared obj, and did a new build world. Same place, same error. - Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Problem Building World
-Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Monday, November 15, 2004 8:10 PM To: Chris Hill Cc: Kevin D. Kinsey, DaleCo, S.P.; Cyber Dog; freebsd- [EMAIL PROTECTED] Subject: Re: Problem Building World On Mon, Nov 15, 2004 at 06:49:22PM -0500, Chris Hill wrote: I did this exact upgrade (4.6 to 4.10) a while back, and I can endorse the 'stepping stone' procedure. I did a cvsup and rebuild from 4.6 to 4.7, 4.7 to 4.8, etc. until 4.10. It's tedious and time-consuming, but the whole thing went surprisingly smoothly. If you have access to the console, you can just avoid the hassle and do a binary upgrade from installation media. Kris This is true, of course. I do have access to the physical machine. The reason I'm hesitant is the research I've done on upgrading has turned up many recommendations that this is usually *not* the best way to go about an upgrade. As I've said, I've never done this before, so I don't know one way or another. Unfortunately this is a business machine, and I'm trying to take the course of least likely destruction. Massive downtime is not good. Of course, I'm making a full backup regardless. - Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
