From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 13:13:24 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 620CC30A; Mon, 11 Mar 2013 13:13:24 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 4333C106; Mon, 11 Mar 2013 13:13:24 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r2BDDIpc057544; Mon, 11 Mar 2013 06:13:18 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r2BDDIJp057543; Mon, 11 Mar 2013 06:13:18 -0700 (PDT) (envelope-from sgk) Date: Mon, 11 Mar 2013 06:13:18 -0700 From: Steve Kargl To: Dimitry Andric Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found Message-ID: <20130311131318.GA57506@troutmask.apl.washington.edu> References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <513DAF4F.50602@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Current , "Hartmann, O." , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 11 Mar 2013 13:13:24 -0000 On Mon, Mar 11, 2013 at 11:17:51AM +0100, Dimitry Andric wrote: > On 2013-03-10 00:39, Steve Kargl wrote: > ... > > If you have a clang built FreeBSD-current, then it is no > > longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor > > the upcoming gcc-4.8.0. AFAICT, the problem is related > > to /usr/bin/cpp. I haven't tried earlier versions of > > gcc. > > I have built the lang/gcc47 and lang/gcc48 ports just now, and they > compiled without any issues. What is the exact error you have been > getting? Note, I said explicitly said *bootstrap*. I can build 4.6, 4.7, and 4.8. I cannot *bootstrap* these compilers. The entire build log from 'gmake bootstrap |& tee gcc-4.8.0.log' is here http://troutmask.apl.washington.edu/gcc-4.8.0.log The last few lines are checking whether /home/sgk/gcc/obj4x/./prev-gcc/xgcc -B/home/sgk/gcc/obj4x/./prev-gcc/ -B/home/sgk/work/4x/x86_64-unknown-freebsd10.0/bin/ -B/home/sgk/work/4x/x86_64-unknown-freebsd10.0/bin/ -B/home/sgk/work/4x/x86_64-unknown-freebsd10.0/lib/ -isystem /home/sgk/work/4x/x86_64-unknown-freebsd10.0/include -isystem /home/sgk/work/4x/x86_64-unknown-freebsd10.0/sys-include supports -fno-rtti... yes checking dependency style of /home/sgk/gcc/obj4x/./prev-gcc/xg++ -B/home/sgk/gcc/obj4x/./prev-gcc/ -B/home/sgk/work/4x/x86_64-unknown-freebsd10.0/bin/ -nostdinc++ -B/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/src/.libs -B/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/libsupc++/.libs -I/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/include/x86_64-unknown-freebsd10.0 -I/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/include -I/home/sgk/gcc/gcc4x/libstdc++-v3/libsupc++ -L/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/src/.libs -L/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/libsupc++/.libs... none configure: error: no usable dependency style found gmake[2]: *** [configure-stage2-libcpp] Error 1 gmake[2]: Leaving directory `/usr/home/sgk/gcc/obj4x' gmake[1]: *** [stage2-bubble] Error 2 gmake[1]: Leaving directory `/usr/home/sgk/gcc/obj4x' gmake: *** [bootstrap] Error 2 > I think there must be a common problem you and Oliver have in your build > environment, most likely non-default CFLAGS. No. Here's my make.conf. KERNCONF=SPEW CPUTYPE?=opteron FFLAGS+= -O2 -pipe -march=native -mtune=native -funroll-loops -ftree-vectorize MALLOC_PRODUCTION="YES" WITHOUT_LIB32="YES" WITHOUT_MODULES="YES" WITHOUT_NLS="YES" WITH_BSD_GREP="YES" WITH_PROFILE="YES" WITH_PKGNG=yes PRINTERDEVICE=ps # # Crap for ports. # DISABLE_MAKE_JOBS="YES" WITH_GHOSTSCRIPT_VER=8 # # added by use.perl 2013-02-19 12:45:06 PERL_VERSION=5.12.4 -- Steve