From owner-freebsd-stable Wed Nov 11 16:58:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00225 for freebsd-stable-outgoing; Wed, 11 Nov 1998 16:58:50 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00220; Wed, 11 Nov 1998 16:58:48 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id QAA23741; Wed, 11 Nov 1998 16:58:20 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 11 Nov 1998 16:58:19 -0800 (PST) From: Doug White To: Florian Nigsch cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Upgrade from 2.2-STABLE to -CURRENT In-Reply-To: <3.0.32.19981111195130.0068d1d0@triton> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Nov 1998, Florian Nigsch wrote: > Hello! > > I have experienced a little problem. In fact, it's a serious problem: :) > > I keep pace with the sourcecodechanges with the CVSup mechanism, and so i > wanted to upgrade my FreeBSD 2.2-STABLE (2.2.7) system to -CURRENT. I read > some docs and Makefiles, found out that the best i could do was to try a > "make aout-to-elf" ind /usr/src. > Now, what I ended up with was the following: How current a -CURRENT? > cp strip maybe_stripped > strip maybe_stripped > *** Error code 1 > ...and five more "*** Error code 1". Hm, it's running the wrong strip(1), I'm guessing. Revision 1.9 of strip's Makefile claims to fix this bug. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message