From owner-freebsd-ports-bugs@FreeBSD.ORG Fri Jul 16 16:11:09 2004 Return-Path: Delivered-To: freebsd-ports-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 725CB16A4CE; Fri, 16 Jul 2004 16:11:09 +0000 (GMT) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC36B43D3F; Fri, 16 Jul 2004 16:11:08 +0000 (GMT) (envelope-from netch@lucky.net) Received: from netch@localhost [127.0.0.1] (netch@localhost [127.0.0.1]) by burka.carrier.kiev.ua with ESMTP id i6GGAxrO038952; Fri, 16 Jul 2004 19:11:02 +0300 (EEST) (envelope-from netch@burka.carrier.kiev.ua) Received: (from netch@localhost) by burka.carrier.kiev.ua (8.12.11/8.12.11/Submit) id i6GGAxpi038949; Fri, 16 Jul 2004 19:10:59 +0300 (EEST) (envelope-from netch) Date: Fri, 16 Jul 2004 19:10:59 +0300 From: Valentin Nechayev To: Gerald Pfeifer Message-ID: <20040716161059.GL1085@lucky.net> References: <20040716094033.GI1085@lucky.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-42: On X-Verify-Sender: verified cc: gerald@freebsd.org cc: ports-bugs@freebsd.org Subject: Re: gcc34 isn't buildable on 4.10 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: netch@lucky.net List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jul 2004 16:11:09 -0000 Fri, Jul 16, 2004 at 14:26:02, gerald wrote about "Re: gcc34 isn't buildable on 4.10": >> does anybody see this? [...] >> ../.././..//gcc-3.4-20040709/libiberty/fibheap.c:166: warning: implicit declarat >> ion of function `free' >> ../.././..//gcc-3.4-20040709/libiberty/fibheap.c: In function `fibheap_delete_no >> de': >> ../.././..//gcc-3.4-20040709/libiberty/fibheap.c:285: error: `LONG_MIN' undeclar [...] > I don't see this, but my 4.x tester is running 4.9-RELEASE-p5 right now; > I do have some doubts that this should be due to the difference from 4.9 > to 4.10, though. It seems you have some additional options set? Well, I've already found that unsetting of CFLAGS in /etc/make.conf fixes building. The values of CFLAGS was: (both 4.10 hosts) CFLAGS= -O -pipe -march=i586 -mcpu=i686 -mpreferred-stack-boundary=2 (4.8 host with the same problem! hence it isn't special for 4.10) CFLAGS= -O2 -pipe -mcpu=i686 -march=i486 -mpreferred-stack-boundary=2 The strangeness is seen in libiberty config log diffs for good variant (without CFLAGS) and bad variant: configure:3410: checking for sys/file.h -configure:3424: /usr/ports/lang/gcc34/work/build/gcc/xgcc -B/usr/ports/lang/gcc 34/work/build/gcc/ -B/usr/local/gcc34-port/i386-portbld-freebsd4.10/bin/ -B/usr/ local/gcc34-port/i386-portbld-freebsd4.10/lib/ -isystem /usr/local/gcc34-port/i3 86-portbld-freebsd4.10/include -isystem /usr/local/gcc34-port/i386-portbld-freeb sd4.10/sys-include -E -O2 conftest.c +configure:3424: /usr/ports/lang/gcc34/work/build/gcc/xgcc -B/usr/ports/lang/gcc 34/work/build/gcc/ -B/usr/local/gcc34-port/i386-portbld-freebsd4.10/bin/ -B/usr/ local/gcc34-port/i386-portbld-freebsd4.10/lib/ -isystem /usr/local/gcc34-port/i3 86-portbld-freebsd4.10/include -isystem /usr/local/gcc34-port/i386-portbld-freeb sd4.10/sys-include -E -O2 -O -pipe -march=i586 -mcpu=i686 -mpreferred-stack-boun dary=2 conftest.c +`-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead. configure:3430: $? = 0 -configure:3450: result: yes +configure: failed program was: +| #line 3416 "configure" +| /* confdefs.h. */ +| +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define BYTEORDER 1234 +| /* end confdefs.h. */ +| #include +configure:3450: result: no configure:3410: checking for sys/param.h -configure:3424: /usr/ports/lang/gcc34/work/build/gcc/xgcc -B/usr/ports/lang/gcc 34/work/build/gcc/ -B/usr/local/gcc34-port/i386-portbld-freebsd4.10/bin/ -B/usr/ local/gcc34-port/i386-portbld-freebsd4.10/lib/ -isystem /usr/local/gcc34-port/i3 86-portbld-freebsd4.10/include -isystem /usr/local/gcc34-port/i386-portbld-freeb sd4.10/sys-include -E -O2 conftest.c +configure:3424: /usr/ports/lang/gcc34/work/build/gcc/xgcc -B/usr/ports/lang/gcc 34/work/build/gcc/ -B/usr/local/gcc34-port/i386-portbld-freebsd4.10/bin/ -B/usr/ local/gcc34-port/i386-portbld-freebsd4.10/lib/ -isystem /usr/local/gcc34-port/i3 86-portbld-freebsd4.10/include -isystem /usr/local/gcc34-port/i386-portbld-freeb sd4.10/sys-include -E -O2 -O -pipe -march=i586 -mcpu=i686 -mpreferred-stack-boun dary=2 conftest.c +`-mcpu=' is deprecated. Use `-mtune=' or '-march=' instead. configure:3430: $? = 0 -configure:3450: result: yes +configure: failed program was: +| #line 3416 "configure" +| /* confdefs.h. */ +| +| #define PACKAGE_NAME "" +| #define PACKAGE_TARNAME "" +| #define PACKAGE_VERSION "" +| #define PACKAGE_STRING "" +| #define PACKAGE_BUGREPORT "" +| #define BYTEORDER 1234 +| /* end confdefs.h. */ +| #include +configure:3450: result: no configure:3410: checking for limits.h All previous tests in libiberty/config.log shows identical results for both cases! Difference begins only from testing for . And, not all following tests fail. The third attempt was on 4.10 with the following CFLAGS: CFLAGS= -O -pipe -march=i686 It bypassed the problematic place. So, is it -mpreferred-stack-boundary? I'll retest as soon as possible. -netch-