From owner-freebsd-ports@FreeBSD.ORG Fri Mar 11 21:43:43 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 328881065670 for ; Fri, 11 Mar 2011 21:43:43 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 148B98FC12 for ; Fri, 11 Mar 2011 21:43:42 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 61EBE5615D; Fri, 11 Mar 2011 15:25:56 -0600 (CST) Date: Fri, 11 Mar 2011 15:25:56 -0600 From: Mark Linimon To: "Klaus T. Aehlig" Message-ID: <20110311212556.GA5331@lonesome.com> References: <20110311105902.GB99056@curry.linta.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110311105902.GB99056@curry.linta.de> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: ports@freebsd.org Subject: Re: science/libctl marked as BROKEN, but does build on 8.2-STABLE amd64 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: Fri, 11 Mar 2011 21:43:43 -0000 On Fri, Mar 11, 2011 at 10:59:02AM +0000, Klaus T. Aehlig wrote: > Can anyone shed more light on why this port is marked BROKEN? In general you have to do a little bit of detective work. First stop: portsmon, to see where it is currently not building: http://portsmon.freebsd.org/portoverview.py?category=science&portname=libctl That only cites sparc64-8 (where the build lags behind the others due to slower hardware). A quick check of the log shows something that is probably sparc64-specific, so let's press on. pointyhat has logs of "when something first failed, and when it most recently failed", that most people don't know about: "new build failures". So let's check in the i386 8 entry: http://pointyhat.freebsd.org/errorlogs/i386-8-failure.html and indeed there's an entry. Failed 20110204, last tried 20110204. Note that the URLs for the errologs here are absolute, not relative, so it will still be valid: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20110223062852/libctl-3.1.log libtool: link: cc -shared .libs/ctl.o .libs/subplex.o .libs/ctl-f77-glue.o .libs/integrator.o .libs/cintegrator.o -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib -pthread -L/usr/local/lib /usr/local/lib/libguile.so /usr/local/lib/libintl.so /usr/local/lib/libiconv.so /usr/local/lib/libgmp.so -lcrypt -lm /usr/local/lib/libltdl.so -Wl,-rpath=/usr/local/lib/gcc45 -pthread -pthread -pthread -pthread -Wl,-soname -Wl,libctl.so.4 -o .libs/libctl.so.4 .libs/ctl.o(.text.__i686.get_pc_thunk.bx+0x0): In function `__i686.get_pc_thunk.bx': : multiple definition of `__i686.get_pc_thunk.bx' /usr/lib/crtbeginS.o(.gnu.linkonce.t.__i686.get_pc_thunk.bx+0x0): first defined here So indeed it broke on i386. Now, generally, when something breaks on i386, it breaks everywhere, but not always. But I'm sure that's why it was marked broken. Unfortunately there's no _easy_ way to see "when was the last time the packaage built on amd64", but if look at "All error logs" / "amd64", you'll get to http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/ Be patient. It will take some time to display :-) The e.* are "error build logs"; the a.* are "all build logs, including errors". It's the latter we will have to walk through: e.g. find the latest one for a.8.2011* and walk back. Now, I've cheated, since i have access to the machine itself, so I did a find, and can tell you it's under a.8.20110224124803: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/a.8.20110224124803/libctl-3.1.log so it indeed built on Feb 24 on amd64. I'll change the BROKEN tag. mcl