Date: Wed, 16 Sep 2015 17:45:51 +0000 From: bugzilla-noreply@freebsd.org To: apache@FreeBSD.org Subject: maintainer-feedback requested: [Bug 203157] www/apache24: mistakenly tries to build expat if old magic files exist while citing a wrong filename Message-ID: <bug-203157-16115-A5CPHx9miF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-203157-16115@https.bugs.freebsd.org/bugzilla/> References: <bug-203157-16115@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
freebsdpr-20121114@billmail.scconsult.com has reassigned Bugzilla Automation <bugzilla@FreeBSD.org>'s request for maintainer-feedback to apache@FreeBSD.org: Bug 203157: www/apache24: mistakenly tries to build expat if old magic files exist while citing a wrong filename https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203157 --- Description --- I tried building ("make build" in www/apache24) apache24 from the port (to get LDAP support not in the binary package) and it chased the textproc/expat2 dependency and tried to install it from the port even though there was a perfectly usable binary package of expat already installed. The output around the detour was: ===> apache24-2.4.16_1 depends on executable: libtoolize - found ===> apache24-2.4.16_1 depends on shared library: libexpat.soEither /usr/share/misc/magic.mime or /usr/share/misc/mime.magic.mgc exist and must be removed. These are legacy files from an older release and may safely be deleted. Please see UPDATING 20150213 for more details. - not found ===> expat-2.1.0_3 depends on file: /usr/local/sbin/pkg - found Note the lack of space after libexpat.so and the 2 file names. I removed /usr/share/misc/magic.mime but /usr/share/misc/mime.magic.mgc did not exist. However /usr/share/misc/magic.mime.mgc DID exist, with the same mtime as /usr/share/misc/magic.mime (suspicious...) "make clean ; make build" resulted in the same detour into building expat with the same error message, even though no such files existed. I removed the suspect file, tried again, and the build went perfectly. This seems like it is maybe 2 bugs, but I'm not sure: 1. /usr/ports/Mk/Scripts/find-lib.sh looks for files of the correct names, emits an error message with one of them mangled. 2. The way /usr/ports/Mk/Scripts/find-lib.sh fails, the message it emits, and the resulting upstream reaction of chasing a dependency unnecessarily is not a recipe for least harm. If those obsolete files are so dangerous that they must break port builds, perhaps the check for them should live somewhere higher up where it can be made to break every port build from the start unconditionally.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203157-16115-A5CPHx9miF>