ports/63272: possible fix for "marked as broken: unknown LIBTOOL version: ."
Scott Bertilson
scott at nts.umn.edu
Mon Feb 23 16:30:35 UTC 2004
>Number: 63272
>Category: ports
>Synopsis: possible fix for "marked as broken: unknown LIBTOOL version: ."
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Feb 23 08:30:34 PST 2004
>Closed-Date:
>Last-Modified:
>Originator: Scott Bertilson
>Release: FreeBSD 4.4-RELEASE-p27 i386
>Organization:
University of Minnesota / OIT
>Environment:
>Description:
bsd.port.mk has:
BROKEN="unknown LIBTOOL version: ${USE_LIBTOOL_VER}"
I'm thinking it should say:
BROKEN="unknown LIBTOOL version: ${WANT_LIBTOOL_VER}"
since "USE_LIBTOOL_VER" can be unset when the code
that generates the "BROKEN" gets executed. "WANT_LIBTOOL_VER"
_is_ set and would have the value of "USE_LIBTOOL_VER"
if the latter had been set, but otherwise has the default.
This would allow the error to actually show a version
instead of nothing.
I would be tempted to go a step farther to change it to:
BROKEN="missing LIBTOOL version: devel/libtool${LIBTOOL_VERSION}"
since that would exactly point to the problem.
>How-To-Repeat:
I ran into this as a result of a ports tree which
was not consistently up to date. Evoke the problem
by:
go into <ports>/devel and hide "libtool*"
("mkdir xx && mv libtool* xx")
go into <ports>/x11-fonts/fontconfig and "make"
"fontconfig" has "USE_LIBTOOL= yes" without
specifying "USE_LIBTOOL_VER" which causes
"WANT_LIBTOOL_VER" to be set, activating the
code in "bsd.port.mk" while "USE_LIBTOOL_VER"
remains unset.
>Fix:
See 2 suggestions in "Description" above.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list