Looks like it's not finding SMB_ACL_T.
That _should_ be acl_t as defined in smb_acl.h
Does chacl work on an XFS mounted file system?
Where are:
acl.h - should be in /usr/include/sys (not /usr/include)
libacl.* - should be in /lib
Does .../source/includes/includes.h have a line
#ifdef HAVE_SYS_ACL_H
#include <sys/acl.h>
#endif
On 18-Sep-2001 Federico Sevilla III wrote:
> Hi everyone,
>
> I'm trying to build the samba-2.2.1a-9 Debian packages and am having
> problems. I'm pretty confident it's not a problem with the build scripts
> of the source because when built without ACL support it goes on fine using
> gcc-3.0.2 (20010908).
>
> Just to make sure I rebuilt all my XFS tools especially acl and acl-dev
> from a current snapshot of the CVS tree. Here now follows a hopefully
> representative subset of the long list of errors that I get:
>
> -----
> include/proto.h:284: warning: data definition has no type or storage class
> include/proto.h:285: parse error before '*' token
> include/proto.h:286: parse error before "entry"
> include/proto.h:287: parse error before "entry"
> include/proto.h:288: parse error before "entry"
> include/proto.h:289: parse error before "theacl"
> include/proto.h:290: parse error before "acl_type_t"
> include/proto.h:291: parse error before "acl_t"
> include/proto.h:293: parse error before "permset"
> include/proto.h:295: parse error before "posix_acl"
> include/proto.h:297: parse error before "the_acl"
> include/proto.h:298: parse error before "entry_d"
> include/proto.h:299: parse error before "entry_d"
> include/proto.h:300: parse error before "entry_d"
> include/proto.h:301: parse error before "sys_acl_get_file"
> include/proto.h:301: parse error before "acl_type_t"
> include/proto.h:301: warning: data definition has no type or storage class
> include/proto.h:302: parse error before "sys_acl_get_fd"
> include/proto.h:302: warning: data definition has no type or storage class
> include/proto.h:303: parse error before "permset"
> include/proto.h:304: parse error before "permset"
> include/proto.h:305: parse error before "permset"
> include/proto.h:306: parse error before "the_acl"
> include/proto.h:308: parse error before "sys_acl_init"
> include/proto.h:308: warning: data definition has no type or storage class
> include/proto.h:309: parse error before '*' token
> include/proto.h:310: parse error before "entry"
> include/proto.h:311: parse error before "entry"
> include/proto.h:312: parse error before "entry"
> include/proto.h:313: parse error before "theacl"
> include/proto.h:314: parse error before "acl_type_t"
> include/proto.h:315: parse error before "acl_t"
> include/proto.h:317: parse error before "the_acl"
> make[1]: *** [smbd/server.o] Error 1
> make[1]: Leaving directory `/home/jijo/build/samba/samba-2.2.1a/source'
> make: *** [build-stamp] Error 2
> -----
>
> Note that the only differences from the "normal" build of the package is
> the "--with-acl-support" directive in configure.
>
> I am wondering (aside from what's wrong): if Samba is configured without
> ACL support, will it still respect permission settings that use ACLs? Or
> will it bypass these altogether? I don't need Windows NT workstations to
> go modifying ACLs since they mess up the execute bits anyway. But I do
> need them to respect ACLs as I'll be implementing ACLs to replace the
> current "valid users" and "write list" so that file access via NFS is
> identical security-wise to Samba.
>
> Thanks in advance to everyone! :)
>
> --> Jijo
>
> --
> Federico Sevilla III :: jijo@xxxxxxxxxxxxxxxxxxxx
> Network Administrator :: The Leather Collection, Inc.
> GnuPG Key: <http://jijo.leathercollection.ph/jijo.gpg>
--
John M. Trostel
Senior Software Engineer
Quantum / SnapAppliances
jtrostel@xxxxxxxxxxxxxx
|