From owner-freebsd-current Tue Nov 19 21:18: 7 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0B8637B401 for ; Tue, 19 Nov 2002 21:18:05 -0800 (PST) Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3418A43E8A for ; Tue, 19 Nov 2002 21:18:05 -0800 (PST) (envelope-from pete@ns.altadena.net) Received: from ns.altadena.net (localhost [127.0.0.1]) by ns.altadena.net (8.12.6/8.12.3) with ESMTP id gAK5Hs8I009428 for ; Tue, 19 Nov 2002 21:17:54 -0800 (PST) (envelope-from pete@ns.altadena.net) Received: (from pete@localhost) by ns.altadena.net (8.12.6/8.12.3/Submit) id gAK5Hrj8009427 for current@freebsd.org; Tue, 19 Nov 2002 21:17:53 -0800 (PST) (envelope-from pete) From: Pete Carah Message-Id: <200211200517.gAK5Hrj8009427@ns.altadena.net> Subject: Re: Strange cross-build problem and something with GEOM To: current@freebsd.org Date: Tue, 19 Nov 2002 21:17:53 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Replying to my own message: --------------------------- > 2 60g drives, ad0 has a complete -stable on it, ad1 current. > > First, GEOM: > On trying to do "boot0cfg -s1 /dev/ad0" to get back to booting stable, > to try to recover from the next problem, I get "operation not permitted". > This didn't happen with NO_GEOM... Is there a new device name to use > here? > > Unfortunately now I can't recover from the next problem without taking > a drive (the system in question is remote; fortunately only a few miles). > > ================== Part 2 ============================= > Now for the cross-build problem: > ---- > On building both stable and current under stable, I get a crippled cpp > in current; it can't do *anything* right, and gets various errors in > various situations. > with source: > ------------ > gooney# cat hello.c > #include > > main() > { > printf("Hello, World!\n"); > } > ------------------------------ > gooney# cc -o hello hello.c > hello.c:1: undefined or invalid # directive > > If I add a comment in the first line, I get: > -------------------------------------------- > gooney# cc -o hello hello.c > hello.c:1: syntax error before `/' > > and the make world under current dies in the very first mkdep, before the > first compile, with another cpp error: > -------------------------------------- Answer is: There was some cruft left over in /usr/bin; copies of cc1 and friends, and cpp0. Apparently the copies in /usr/libexec get ignored if the progs exist in /usr/bin. Cleaning those (and a couple of old copies of perl too :-) out fixed the problem. Now to get it so boot0cfg works under GEOM... -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message