From owner-freebsd-current@FreeBSD.ORG Mon Oct 10 01:18:35 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF6FD106567F for ; Mon, 10 Oct 2011 01:18:35 +0000 (UTC) (envelope-from null@pozo.com) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.freebsd.org (Postfix) with ESMTP id 67B318FC12 for ; Mon, 10 Oct 2011 01:18:35 +0000 (UTC) Received: from T61p.pozo.com (t61p.pozo.com [192.168.0.4]) (authenticated bits=0) by pozo.com (8.14.5/8.14.5) with ESMTP id p9A1IJ0K005636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 9 Oct 2011 18:18:19 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <201110100118.p9A1IJ0K005636@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 09 Oct 2011 18:18:13 -0700 To: "Conrad J. Sabatier" , freebsd-current@freebsd.org From: Manfred Antar In-Reply-To: <20111009135735.3f5fe1c1@cox.net> References: <4E919228.8010708@zedat.fu-berlin.de> <201110091548.p99FmpF4018785@pozo.com> <20111009135735.3f5fe1c1@cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, score=-101.4 required=5.0 tests=ALL_TRUSTED,MISSING_MID, RP_MATCHES_RCVD, USER_IN_WHITELIST autolearn=unavailable version=3.3.2, No X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on pozo.com X-pozocom-MailScanner-Information: Please contact the ISP for more information X-pozocom-MailScanner-ID: p9A1IJ0K005636 X-pozocom-MailScanner: Found to be clean X-pozocom-MailScanner-From: null@pozo.com Cc: Subject: Re: FreeBSD 10.0-CURRENT: messed up the ports and system (gcc46 won't compile) and need to repair - how? 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: Mon, 10 Oct 2011 01:18:36 -0000 At 11:57 AM 10/9/2011, Conrad J. Sabatier wrote: >On Sun, 09 Oct 2011 08:48:46 -0700 >Manfred Antar wrote: > >> Did you rebuild ports/devel/binutils after change to 10.0 current. >> I was having same problem with gcc45 , then i rebuilt binutils with >> uname_r 9.0-Current and it went away. > >Actually, binutils built just fine for me just now without setting >UNAME_r under current. > >-- >Conrad J. Sabatier >conrads@cox.net Built fine for me too. But when I tried to compile gcc45 no go recompiled binutils with uname_r 9.0-CURRENT, And gcc45 built fine. so my assumption was that something gets messed up with the binutils and gcc45 when built with current. ======================== || null@pozo.com || || Ph. (415) 681-6235 || ======================== -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.