From owner-freebsd-ports@FreeBSD.ORG Sun Jun 10 17:26:03 2007 Return-Path: X-Original-To: freebsd-ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BF7B216A400 for ; Sun, 10 Jun 2007 17:26:03 +0000 (UTC) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn.kn-bremen.de [212.63.36.242]) by mx1.freebsd.org (Postfix) with ESMTP id 7A29913C487 for ; Sun, 10 Jun 2007 17:26:03 +0000 (UTC) (envelope-from nox@saturn.kn-bremen.de) Received: by gwyn.kn-bremen.de (Postfix, from userid 10) id 9CB2019DDE7; Sun, 10 Jun 2007 19:26:01 +0200 (CEST) Received: from saturn.kn-bremen.de (nox@localhost [127.0.0.1]) by saturn.kn-bremen.de (8.13.6/8.13.6) with ESMTP id l5AHNl5K025796 for ; Sun, 10 Jun 2007 19:23:47 +0200 (CEST) (envelope-from nox@saturn.kn-bremen.de) Received: (from nox@localhost) by saturn.kn-bremen.de (8.13.6/8.13.6/Submit) id l5AHNkt1025795 for freebsd-ports@FreeBSD.org; Sun, 10 Jun 2007 19:23:46 +0200 (CEST) (envelope-from nox) From: Juergen Lock Date: Sun, 10 Jun 2007 19:23:46 +0200 To: freebsd-ports@FreeBSD.org Message-ID: <20070610172346.GA24952@saturn.kn-bremen.de> Mail-Followup-To: freebsd-ports@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.14 (2007-02-12) Cc: Subject: USE_GCC weirdness - http://bento.freebsd.org/errorlogs/amd64-7-latest-logs/qemu-devel-0.9.0s.20070526.log 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, 10 Jun 2007 17:26:03 -0000 Hi! Does anyone have an idea whats happening here? It builds on i386, http://bento.freebsd.org/errorlogs/i386-7-latest-logs/qemu-devel-0.9.0s.20070526.log and when I queued it on tb3 (which also is amd64) it built too, http://tb3.droso.net/logs/7-nox/qemu-devel-0.9.0s.20070526.log (only change being I added logging (${SH} -x) to the configure invocation.) The failed build is also missing the ===> qemu-devel-0.9.0s.20070526 depends on executable in : gcc34 - found line, although BUILD_DEPENDS is logged as having gcc-3.4.6_1,1.tbz in there... Ok maybe some explanations: qemu doesnt build with gcc4, so it has USE_GCC= 3.4 and CONFIGURE_ARGS+= --prefix=${PREFIX} --cc=${CC} and when qemu's configure script detects gcc4 it prints a warning and exits. What I don't get is why BUILD_DEPENDS gets lost here, and only `sometimes'... (There already was one report of this happening as some may remember, and miwi couldn't reproduce it, http://miwi.homeunix.com/tb/logs/7.0-HEAD/qemu-devel-0.9.0s.20070526.log ) Also I just noticed the 0.9.0 qemu port now failed too, http://bento.freebsd.org/errorlogs/amd64-7-latest-logs/qemu-0.9.0_3.log and it certainly did build before, http://pointyhat.freebsd.org/errorlogs/amd64-7-latest-logs/qemu-0.9.0_3.log (only change being a new MASTER_SITE...) WTF!?? Juergen