From owner-freebsd-current@FreeBSD.ORG Fri Sep 26 19:27:36 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B2D91065689 for ; Fri, 26 Sep 2008 19:27:36 +0000 (UTC) (envelope-from peter@wemm.org) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.179]) by mx1.freebsd.org (Postfix) with ESMTP id 2DFF48FC0C for ; Fri, 26 Sep 2008 19:27:36 +0000 (UTC) (envelope-from peter@wemm.org) Received: by el-out-1112.google.com with SMTP id v27so261449ele.13 for ; Fri, 26 Sep 2008 12:27:35 -0700 (PDT) Received: by 10.142.240.9 with SMTP id n9mr763265wfh.79.1222456773405; Fri, 26 Sep 2008 12:19:33 -0700 (PDT) Received: by 10.142.255.21 with HTTP; Fri, 26 Sep 2008 12:19:33 -0700 (PDT) Message-ID: Date: Fri, 26 Sep 2008 12:19:33 -0700 From: "Peter Wemm" To: "Marcel Moolenaar" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080926124026.0570973039@freebsd-current.sentex.ca> <20080926125641.GU47828@deviant.kiev.zoral.com.ua> Cc: Kostik Belousov , current@freebsd.org, ia64@freebsd.org Subject: Re: [head tinderbox] failure on ia64/ia64 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: Fri, 26 Sep 2008 19:27:36 -0000 On Fri, Sep 26, 2008 at 8:05 AM, Marcel Moolenaar wrote: > > On Sep 26, 2008, at 5:56 AM, Kostik Belousov wrote: > >> On Fri, Sep 26, 2008 at 08:40:25AM -0400, FreeBSD Tinderbox wrote: >>> >>> TB --- 2008-09-26 12:27:35 - tinderbox 2.3 running on >>> freebsd-current.sentex.ca >>> TB --- 2008-09-26 12:27:35 - starting HEAD tinderbox run for ia64/ia64 >>> TB --- 2008-09-26 12:27:35 - cleaning the object tree >>> TB --- 2008-09-26 12:28:10 - cvsupping the source tree >>> TB --- 2008-09-26 12:28:10 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s >>> /tinderbox/HEAD/ia64/ia64/supfile >>> TB --- 2008-09-26 12:28:17 - building world (CFLAGS=-O -pipe) >>> TB --- 2008-09-26 12:28:17 - cd /src >>> TB --- 2008-09-26 12:28:17 - /usr/bin/make -B buildworld >>>>>> >>>>>> World build started on Fri Sep 26 12:28:19 UTC 2008 >>>>>> Rebuilding the temporary build tree >>>>>> stage 1.1: legacy release compatibility shims >>>>>> stage 1.2: bootstrap tools >>>>>> stage 2.1: cleaning up the object tree >>>>>> stage 2.2: rebuilding the object tree >>>>>> stage 2.3: build tools >>>>>> stage 3: cross tools >>>>>> stage 4.1: building includes >>>>>> stage 4.2: building libraries >>> >>> [...] >>> building static gcc library >>> ranlib libgcc.a >>> sh /src/tools/install.sh -C -o root -g wheel -m 444 libgcc_eh.a >>> /obj/ia64/src/tmp/usr/lib >>> sh /src/tools/install.sh -C -o root -g wheel -m 444 libgcc.a >>> /obj/ia64/src/tmp/usr/lib >>> ===> gnu/lib/csu (obj,depend,all,install) >>> cc -O -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 >>> -finhibit-size-directive -fno-inline-functions -fno-exceptions >>> -fno-zero-initialized-in-bss -fno-zero-initialized-in-bss >>> -fno-toplevel-reorder -I/src/gnu/lib/csu/../../../contrib/gcclibs/include >>> -I/src/gnu/lib/csu/../../../contrib/gcc/config >>> -I/src/gnu/lib/csu/../../../contrib/gcc -I. >>> -I/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -x assembler-with-cpp -include >>> osreldate.h -std=gnu89 -g0 -DCRT_BEGIN -c -o crtbegin.o >>> /src/gnu/lib/csu/../../../contrib/gcc/config/ia64/crtbegin.asm >>> /obj/ia64/src/tmp/usr/include/osreldate.h: Assembler messages: >>> /obj/ia64/src/tmp/usr/include/osreldate.h:38: Error: Unknown opcode >>> `extern int getosreldate(void)' >>> *** Error code 1 >>> >>> Stop in /src/gnu/lib/csu. >>> *** Error code 1 >> >> May be the right location for getosreldate() prototype is unistd.h then. >> Do you agree ? > > I just fixed it by adding -D_OSRELDATE_H to CFLAGS. This prevents the > prototype from being declared while still defining __FreeBSD_version. > In theory -- I haven't tested it yet... The question is.. how is __STDC__ getting set for asm code? It most definitely is not "standard C" code. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell