[Bug 203157] www/apache24: mistakenly tries to build expat if old magic files exist while citing a wrong filename

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Sep 16 17:45:53 UTC 2015


            Bug ID: 203157
           Summary: www/apache24: mistakenly tries to build expat if old
                    magic files exist while citing a wrong filename
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: apache at FreeBSD.org
          Reporter: freebsdpr-20121114 at billmail.scconsult.com
          Assignee: apache at FreeBSD.org
             Flags: maintainer-feedback?(apache at FreeBSD.org)

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
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.

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-apache mailing list