On Sep 26, 2008, at 3:58 PM, Scot Hetzel wrote:
On Fri, Sep 26, 2008 at 11:36 AM, Erik Van Benschoten
<[EMAIL PROTECTED]> wrote:
On Sep 26, 2008, at 10:27 AM, Scot Hetzel wrote:
Then when a
make install was performed, the recycle.so module was located in the
PREFIX/lib/samba/vfs directory.
Did you check this directory?
Scot
Scot,
The problem was not getting the VFS modules compiled, but rather
getting
them installed.
The VFS modules are installed on my system, and when i grepped the
+CONTENTS file for recycle.so, it was listed in the package.
I found a brute force workaround was to manually add
'lib/samba/vfs/recycle.so' to the '/net/samba3/pkg-plist' file.
I know this is not the proper thing to do, but it works for getting a
package built. I would have preferred a tweak to the Makefile that
would
work for everyone, but I'm afraid my Makefile reading skills are
not up to snuff.
There is no need to add 'lib/samba/vfs/recycle.so' to the
samba3/pkg-plist, as the samba3/Makefile has automatic pkg-plist
generation to detect the files in PREFIX/lib/samba. They get added
to the ${TMPPLIST} file, which is used to create the package.
Scot
Interesting. I did a 'make rmconfig' to clean out any old cruft
followed my a 'make package-recursive' (selecting ACL_SUPPORT and
EXP_MODULES along with the defaults). The vfs modules are being
installed on the build machine and are also in the package now
according to a 'pkg_info -L'. I have been using make.conf to customize
my package builds up to this point instead of the 'make config'
mechanism. I guess I'll have to take a closer look into why the builds
didn't work properly the other way. Thanks for the response.
Erik
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
