==>Entering directory /home/pyarra/bacula-5.0.1/src/findlib make: Entering directory `/home/pyarra/bacula-5.0.1/src/findlib' Compiling attribs.c attribs.c: In function `void encode_stat(char*, stat*, int, int)': attribs.c:211: error: 'struct stat' has no member named 'st_flags' attribs.c: In function `int decode_stat(char*, stat*, int32_t*)': attribs.c:308: error: 'struct stat' has no member named 'st_flags' attribs.c:310: error: 'struct stat' has no member named 'st_flags' attribs.c: In function `bool set_attributes(JCR*, ATTR*, BFILE*)': attribs.c:482: error: 'struct stat' has no member named 'st_flags' attribs.c:482: error: `chflags' undeclared (first use this function) attribs.c:482: error: (Each undeclared identifier is reported only once for each function it appears in.) make: *** [attribs.lo] Error 1 make: Leaving directory `/home/pyarra/bacula-5.0.1/src/findlib' ====== Error in /home/pyarra/bacula-5.0.1/src/findlib ======
My latest attempt to cross-compile for sparc has meant setting up an Ubuntu 10,04 box, and I'm currently following this guide to get the cross-compile tools set up. It's not an area I know much about - although I "get" the theory behind cross-compiling, in the past, I've always just kept a build host for each architecture I'm building for (ultrasparc, alpha) and battled with drain-bamaged build environmnts as best I could. Hopefully, this initial pain of setting up a cross-compile environment will be worth it.
So far so good, then install libpq-dev (so I can --with-postgresql - you need to specify one DB to support when you compile, as there's no way to compile only the storage daemon).
Then ./configure --with-postgresql --host=sparc-linux-gnu and of course it bombs out here:
checking whether setpgrp takes no argument... configure: error: cannot check setpgrp when cross compiling
Agh, well how about not checking for it then?? I guess one day I'll have to learn how to use autoconf so I can fix this properly, but for now, edit configure to skip this check.