From owner-freebsd-current@FreeBSD.ORG Sat Mar 10 05:54:03 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 46023106566C for ; Sat, 10 Mar 2012 05:54:03 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmfepo102.cox.net (eastrmfepo102.cox.net [68.230.241.214]) by mx1.freebsd.org (Postfix) with ESMTP id D17DB8FC12 for ; Sat, 10 Mar 2012 05:54:02 +0000 (UTC) Received: from eastrmimpo306.cox.net ([68.230.241.238]) by eastrmfepo102.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20120310055357.IBFY26743.eastrmfepo102.cox.net@eastrmimpo306.cox.net>; Sat, 10 Mar 2012 00:53:57 -0500 Received: from serene.no-ip.org ([98.164.84.176]) by eastrmimpo306.cox.net with bizsmtp id jhtw1i00C3oG0Ji02htwYX; Sat, 10 Mar 2012 00:53:56 -0500 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020207.4F5AEC74.007D,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=1.1 cv=JAjkWMCoDZF0WXzySLmL90Kg4Ce3QIIjGOzsRGfHJ3k= c=1 sm=1 a=G8Uczd0VNMoA:10 a=kj9zAlcOel0A:10 a=qwmwShWo9LG1Fa0ONy89vg==:17 a=kviXuzpPAAAA:8 a=WqMwxfAy8TransvnxHsA:9 a=5-OWygApi7nr6LT98eIA:7 a=CjuIK1q_8ugA:10 a=4vB-4DCPJfMA:10 a=qwmwShWo9LG1Fa0ONy89vg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from cox.net (localhost [127.0.0.1]) by serene.no-ip.org (8.14.5/8.14.5) with ESMTP id q2A5rt6o098960; Fri, 9 Mar 2012 23:53:56 -0600 (CST) (envelope-from conrads@cox.net) Date: Fri, 9 Mar 2012 23:53:50 -0600 From: "Conrad J. Sabatier" To: freebsd-current@freebsd.org Message-ID: <20120309235350.7422a1fe@cox.net> In-Reply-To: <20120309233822.789ad2cf@cox.net> References: <20120309140408.42f136d5@cox.net> <4F5A788B.8090907@mail.zedat.fu-berlin.de> <20120309233822.789ad2cf@cox.net> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "O. Hartmann" Subject: Re: More of that "Rune" business X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Mar 2012 05:54:03 -0000 On Fri, 9 Mar 2012 23:38:22 -0600 "Conrad J. Sabatier" wrote: > On Fri, 09 Mar 2012 22:39:23 +0100 > "O. Hartmann" wrote: > > > On 03/09/12 21:04, Conrad J. Sabatier wrote: > > > I'm getting quite a few of these "Rune"-related errors during port > > > builds lately. I've tried following the advice from the list, but > > > no good, they still keep occurring. I even tried backing off to > > > my last known good buildworld/buildkernel (around Feb 23), and it > > > still doesn't help. > > > > > > Also seeing problems relating to the new clang src.conf variables. > > > Can't successfully build world and/or kernel to try to correct > > > things. "make buildenv" in /usr/src hasn't helped. "make install" > > > in /usr/src/share/mk hasn't helped. > > > > > > Is there some "magic bullet" for this that I've just somehow > > > managed to overlook? I'm totally at a loss here. Help! [failed port build output snipped] > > Me, too, here. > > Buidling a world with most recent sources and CLANG doesn't work, if > > building with legacy/old gcc 4.2.1 the option WITH_LIBCPLUSPLUS= > > YES blow off things. > > > > I had the "_Rune" problem quite often and came around by walking > > back to a well known source base and doing a "make installincludes". > > Yes, it's a very frustrating issue, because it also affects ports > builds, not only source. > > Just on the outside chance it might help, tonight I hosed my entire > src tree (which I normally update from a local copy of the CVS > repository which I maintain via csup) and did an svn checkout of the > src tree. Still no go. Same exact thing. > > I'm completely stuck for the time being, until the root cause of this > problem is corrected. I only have about a 50/50 chance at the moment > of any port builds succeeding, with numerous updates lying in wait, > and zero chance of a successful world/kernel build. I don't pretend > to understand what the real issue is; all I do know is what I've been > seeing lately: numerous failed ports builds, most of them referring to > an unresolvable _ThreadRuneLocale, and some of them mentioning issues > with yylex et al. I'm stumped, honestly. Been reading the lists in > hopes of learning of a working solution, but nothing I've tried so > far has produced any positive results. I'm seeing the word "Rune" in > my sleep lately, I swear! :-) > > This is absolutely maddening! Well, now, this is interesting. Just for curiosity's sake, I tried building a new kernel with the fresh source tree I just fetched from the svn repository, and it succeeded! Still can't build world, though. The question now is: do I dare install this new kernel and give it a try? Cant afford to do any harm to my existing installation. My latest working kernel is from Feb 23. Just how dangerous might it be to try the new one? -- Conrad J. Sabatier conrads@cox.net