The option I use to do these sorts of installs when I have binary compatible systems is to do a "make" for each type, then just "make install" off the NFS mount.
--Bryan On Mar 12, 2012, at 5:33 PM, Forrest Aldrich wrote: > I've run into a quirky issue with installing ClamAV from an NFS mount. I do > this to keep the same code available to all my systems. I have separate > mounts for 32- and 64-bit. > > For ClamAV, the installation will fail because the NFS mount itself is > read-only (ro): > > make[3]: Entering directory `/local/dist/clamav/clamav-0.97.3/libclamav' > GEN version.h.tmp > rm: cannot remove `version.h.tmp': Read-only file system > touch: cannot touch `version.h.tmp': Read-only file system > > Without digging into how this works, I believe I see what's going on -- but I > wonder if there's a clever way around this. I really don't want to go > through and change the mounts to read-write -- they are read-only for a > reason -- or copy the code over and install each individually. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
