From owner-freebsd-current@FreeBSD.ORG Sat Mar 9 16:57:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E7B2F3D3; Sat, 9 Mar 2013 16:57:35 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 5586FFC5; Sat, 9 Mar 2013 16:57:35 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1UEN5S-001qH1-Jj>; Sat, 09 Mar 2013 17:57:34 +0100 Received: from e178004056.adsl.alicedsl.de ([85.178.4.56] helo=munin.geoinf.fu-berlin.de) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtpsa (envelope-from ) id <1UEN5S-003Skc-9a>; Sat, 09 Mar 2013 17:57:34 +0100 Message-ID: <513B6A3E.1030306@zedat.fu-berlin.de> Date: Sat, 09 Mar 2013 17:58:38 +0100 From: "Hartmann, O." Organization: FU Berlin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130309 Thunderbird/17.0.4 MIME-Version: 1.0 To: Dimitry Andric Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> In-Reply-To: <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> Content-Type: multipart/mixed; boundary="------------010909040709020401000602" X-Originating-IP: 85.178.4.56 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Current , 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: Sat, 09 Mar 2013 16:57:36 -0000 This is a multi-part message in MIME format. --------------010909040709020401000602 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Am 03/09/13 17:02, schrieb Dimitry Andric: > On Mar 9, 2013, at 16:36 , "Hartmann, O." wrote: >> I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0 >> r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build >> either lang/gcc or lang/gcc46 with the very same error shown below. > … >> checking whether cc supports -pedantic -Wno-long-long... yes >> checking dependency style of cc... none >> configure: error: no usable dependency style found >> gmake[2]: *** [configure-stage1-libcpp] Error 1 >> gmake[2]: Leaving directory `/usr/ports/lang/gcc/work/build' >> gmake[1]: *** [stage1-bubble] Error 2 >> gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build' >> gmake: *** [all] Error 2 >> *** [do-build] Error code 1 > > What is the actual error in the resulting config.log file? Unfortunately autoconf error message are virtually information-free… > > My first guess would be that you have non-default CFLAGS in your build environment, which confuse gcc's build stages. Hello. CFLAGS settings are either root@thor:/usr/ports/lang/gcc # make -VCFLAGS -O2 -pipe -march=native -I/usr/local/include -fno-strict-aliasing or root@thor:/usr/ports/lang/gcc # make -VCFLAGS -O2 -pipe -O3 -march=native -I/usr/local/include -fno-strict-aliasing There are several config.log files: ./work/build/config.log ./work/build/lto-plugin/config.log ./work/build/gcc/config.log ./work/build/intl/config.log ./work/build/libcpp/config.log ./work/build/build-x86_64-portbld-freebsd10.0/libiberty/config.log ./work/build/build-x86_64-portbld-freebsd10.0/fixincludes/config.log ./work/build/libiberty/config.log Most recent touched is ./work/build/libcpp/config.log and since libcpp occurs in the error, it is the requested log file. I can not see anything useful in that file - I'm sorry :-( It is attached to this post. If you need further material, feel free to ask. By the way, I copied my /etc/make.conf and /etc/src.conf to another CURRENT machine which has the very same revision status (as well as the /usr/src AND /usr/ports, both boxes are up to date even with "portmaster" run this morning). I do not see the problem on this other machine. --------------010909040709020401000602--