Re: Need help on Bacula FTBFS
On Mon, 2010-02-22 at 19:53:26 +0100, Petr Salinger wrote:
> The error is shown in buildd log, but the build
> should bail out much earlier:
> Compiling acl.c
> acl.c: In function 'bacl_exit_code build_acl_streams(JCR*, FF_PKT*)':
> acl.c:1233: error: 'os_build_acl_streams' was not declared in this scope
> acl.c: In function 'bacl_exit_code parse_acl_streams(JCR*, int)':
> acl.c:1249: error: 'os_parse_acl_streams' was not declared in this scope
> acl.c:1254: error: 'os_parse_acl_streams' was not declared in this scope
> acl.c:1258: error: 'os_access_acl_streams' was not declared in this scope
> acl.c:1266: error: 'os_default_acl_streams' was not declared in this scope
> acl.c: At global scope:
> acl.c:72: warning: 'bacl_exit_code send_acl_stream(JCR*, int)'
> defined but not used
> make: *** [acl.o] Error 1
> >2) Bacula 3.0.0 built fine on both of these platforms. Unsure if the
> >present failure is due to a change in Bacula or in the platform.
> Please explicitely disable ACL and xattr,
> idea build tested as shown bellow.
This will imply a lose of functionality, also it seems to me the real
problem is that there's no HAVE_*_OS macro being defined from
“autoconf/bacula-macros/os.m4” which will cause other issues (at
run-time probably). I've not checked all instances of their usage but
some seem to be needed when using a FreeBSD kernel (and not a whole
FreeBSD system), like in “src/stored/dev.c” where it handles “block”
devices as “char” devices on kFreeBSD.
Some of the system checks would benefit from being switched to be
feature checks instead, the BA_CHECK_OPSYS one could use the gnu
triplet instead from AC_CANONICAL_HOST.