science/libctl marked as BROKEN, but does build on 8.2-STABLE
linimon at lonesome.com
Fri Mar 11 21:43:43 UTC 2011
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:
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:
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:
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
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:
so it indeed built on Feb 24 on amd64.
I'll change the BROKEN tag.
More information about the freebsd-ports