From owner-freebsd-questions Tue Feb 13 1:32:12 2001 Delivered-To: freebsd-questions@freebsd.org Received: from web5202.mail.yahoo.com (web5202.mail.yahoo.com [216.115.106.170]) by hub.freebsd.org (Postfix) with SMTP id 8B4FF37B491 for ; Tue, 13 Feb 2001 01:32:08 -0800 (PST) Message-ID: <20010213093208.12826.qmail@web5202.mail.yahoo.com> Received: from [64.170.164.211] by web5202.mail.yahoo.com; Tue, 13 Feb 2001 01:32:08 PST Date: Tue, 13 Feb 2001 01:32:08 -0800 (PST) From: Alex Teslik Reply-To: teslik@yahoo.com Subject: 3.2R to 4.2R upgrade issues To: freebsd-questions@freebsd.org Cc: teslik@yahoo.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear List, I really enjoy using FreeBSD and love the work people do on it, but I am concerned about the upgrade procedure and it's level of unreliability. At first I tried to upgrade to 4.2R directly from 3.2R by CVSUP all of usr/src/, then make world. This gave me an error related to libc in which perl could not find setresuid and setresgid because they are calls that were not present until libc.so.4. So, after digging through the lists I found an idea to link to the new libc during building by using ldconfig. This also did not work. Then I found a recommendation to upgrade to 4.0 first, then up to 4.2. Based on this advice, I erased all of /usr/src/, then all of /usr/obj. I then CVSUP all of 4.0 src and ports successfully. Now, when I run make buildworld (the first step in UPGRADE.txt) I get the following output: install: /usr/src/gnu/lib/libobjc/../../../contrib/gcc/objc/hash.h: No such file or directory *** Error code 71 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Going through the list I can see that many people are having these sorts of problems where src does not compile correctly. I am willing to continue my dig through the lists until I make it work on my system, and any help would be greatly appreciated. However, I think it is in the best interest of the project to make sure that RELEASE versions can compile reliably from previous versions since they are by design complete versions of the system. I can understand these types of problems with STABLE and CURRENT - thats what they are for, but RELEASE should be self-contained. I think I'm not the only one with this problem since when I checked the stats to freebsd.org I noticed that very few of the hits are coming from systems running anything above 3.4. I think the upgrade procedure plays a hand in that. I don't have a lot of programming experience or knowledge, but if there is anything I can do please let me know. Alex p.s.- please reply to , I'm not subscribed. __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message