[MacPorts] #31672: clamav 0.97.3 not building on OS/X Lion 10.7.2 b/c of "missing" clamav user
MacPorts
noreply at macports.org
Tue Oct 18 21:07:01 PDT 2011
#31672: clamav 0.97.3 not building on OS/X Lion 10.7.2 b/c of "missing" clamav user
-----------------------------------------+----------------------------------
Reporter: captainproton1971@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.0.3
Keywords: | Port:
-----------------------------------------+----------------------------------
''(I think this might be related to ticket #31154)''
Looking at the output of port -v install clamav, it seems that the
configure script is looking for a file /usr/bin/nidump which hasn't been
part of OS/X since 10.5. For some reason, the configure script run by
MacPorts seems to trying nidump rather than dscl.
The relevant output is
{{{
bash-3.2# port install clamav
---> Computing dependencies for clamav
---> Configuring clamav
}}}
(blah blah blah)...
{{{
checking for sched_yield... yes
checking for pthread_yield... no
checking for enable_extended_FILE_stdio... no
checking for readdir_r... support disabled
checking for ctime_r... yes, and it takes 2 arguments
checking for socklen_t... yes
checking for clamav in /etc/passwd... checking for clamav using netinfo...
./configure: line 17550: /usr/bin/nidump: No such file or directory
./configure: line 17551: /usr/bin/nidump: No such file or directory
no
configure: error: User clamav (and/or group clamav) doesn't exist. Please
read the documentation !
}}}
Interestingly enough, I can successfully configure (./configure) and
compile (make) from the
/opt/local/var/macports/sources/rsync.macports.org/release/ports/sysutils/clamav
directory. In doing this, it seems that the configure script uses dscl
rather than nidump.
{{{
bash-3.2# ./configure | grep passwd
rm: conftest.so.dSYM: is a directory
checking for clamav in /etc/passwd... checking for clamav using dscl...
yes, user clamav and group clamav
}}}
I'm guessing that there are some configure options being passed by the
Portfile that are interfering, but I'm not clever enough to locate the
problem.
--
Ticket URL: <https://trac.macports.org/ticket/31672>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list