From owner-freebsd-current Thu Oct 31 16:39:17 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 B953E37B401 for ; Thu, 31 Oct 2002 16:39:15 -0800 (PST) Received: from ip68-14-62-49.no.no.cox.net (ip68-14-62-49.no.no.cox.net [68.14.62.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C37643E42 for ; Thu, 31 Oct 2002 16:39:15 -0800 (PST) (envelope-from conrads@cox.net) Received: from ip68-14-62-49.no.no.cox.net (localhost [127.0.0.1]) by ip68-14-62-49.no.no.cox.net (8.12.6/8.12.6) with ESMTP id gA10d5CW028153 for ; Thu, 31 Oct 2002 18:39:10 -0600 (CST) (envelope-from conrads@ip68-14-62-49.no.no.cox.net) Received: (from conrads@localhost) by ip68-14-62-49.no.no.cox.net (8.12.6/8.12.6/Submit) id gA10d0H5028152 for current@FreeBSD.ORG; Thu, 31 Oct 2002 18:39:00 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 31 Oct 2002 18:39:00 -0600 (CST) Reply-To: conrads@cox.net Organization: A Rag-Tag Band of Drug-crazed Hippies From: Conrad Sabatier To: current@FreeBSD.ORG Subject: A few questions 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 I just upgraded a 4.7-STABLE box to current over the weekend. Went off very well, thanks to the great documentation in UPDATING. It's odd, though, that after upgrading again just a few days later, suddenly X (or perhaps just xdm) failed to start due to an unresolved symbol. I had already upgraded X, as well as many other ports, after upgrading to -current, btw. It seems very peculiar that a cvsup just a few days apart from the previous one would require X to be rebuilt. On another note, can someone clue me in as to why I'm getting all these "duplicate script" errors when building both ports and world? I've looked high and low and can't find the reason for this. Seems harmless enough, but it *is* just slightly annoying. And finally, is there a simple way to ensure that none of the debugging code (including INVARIANTS stuff) is included during a buildworld? It would be nice if there were a simple switch or environment variable to control this. Please forgive if this is all old stuff; I'm new with -current, and I have made a real effort to find the answers to this stuff myself. Thanks. -- Conrad Sabatier One Page Principle: A specification that will not fit on one page of 8.5x11 inch paper cannot be understood. -- Mark Ardis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message