From owner-freebsd-ports@FreeBSD.ORG Sun Oct 9 16:03:15 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5C18106566C; Sun, 9 Oct 2011 16:03:15 +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 2A6368FC0A; Sun, 9 Oct 2011 16:03:14 +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 p99FmpF4018785 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 9 Oct 2011 08:48:52 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <201110091548.p99FmpF4018785@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 09 Oct 2011 08:48:46 -0700 To: "Hartmann, O." , freebsd-current , freebsd-ports@freebsd.org From: Manfred Antar In-Reply-To: <4E919228.8010708@zedat.fu-berlin.de> References: <4E919228.8010708@zedat.fu-berlin.de> 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: p99FmpF4018785 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-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Oct 2011 16:03:15 -0000 At 05:23 AM 10/9/2011, Hartmann, O. wrote: >Since the change of one of my boxes to FreeBSD 10.0 and some >accindetally build of ports without the suggested settings for UNAME_r >before building ports, I think I've messed up with some ports and need >some advice how to fixate the problem. > >Some develish motivation drove me today building gcc46/gotoblas and gcc >fails to build with the below shown message. But this is not the only >port that rushes into problems. > >Thing is: I do not know wether I messed up the system or this is simply >the very often mentioned problem due to the two-digit versioning of the >most recent CURRENT. > >Except ANJUTA, which complains about a non-working subversion module due >to some lack in a libgdbm port (which also won't build) everything works >fine and I can stand this for the next one or two weeks to wait for a >general fixation, but it would be a good attempt, I think, to start >fixating my messed up system now, if there is any real mess I did. > >Any advice? > > >Thanks in advance. > >Oliver > >P.S.: On FreeBSD 9.0-BETA3 everything runs well, except the usual little >horror with legacy gcc 4.2 versus CLANG. So I expect the problems to be >real 10.0-issues. > >=== > > >checking for suffix of object files... configure: error: in >`/usr/ports/lang/gcc46/work/build/x86_64-portbld-freebsd10.0/libgcc': >configure: error: cannot compute suffix of object files: cannot compile >See `config.log' for more details. >gmake[2]: *** [configure-stage1-target-libgcc] Error 1 >gmake[2]: Leaving directory `/usr/ports/lang/gcc46/work/build' >gmake[1]: *** [stage1-bubble] Error 2 >gmake[1]: Leaving directory `/usr/ports/lang/gcc46/work/build' >gmake: *** [bootstrap-lean] Error 2 >*** Error code 1 > >Stop in /usr/ports/lang/gcc46. >*** Error code 1 > >Stop in /usr/ports/lang/gcc46. > >===>>> make failed for lang/gcc46 >===>>> Aborting update > >===>>> Update for lang/gcc46 failed >===>>> Aborting update > >_______________________________________________ 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. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.