Arch Linux User Repository

Version 5.1.9 not building properly. Dependencies are handled as expected, but then when autofs starts its build process, it throws the following error related to cyrus-sasl.o:

strip --strip-debug mount_ext2.so
strip --strip-debug lookup_dir.so
strip --strip-debug mount_bind.so
strip --strip-debug lookup_hosts.so
strip --strip-debug mount_autofs.so
strip --strip-debug lookup_multi.so
cyrus-sasl.c:112:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int,  const char **, unsigned int *)’ [-Wincompatible-pointer-types]
  112 |         { SASL_CB_USER, &getuser_func, NULL },
      |                         ^
cyrus-sasl.c:112:25: note: (near initialization for ‘callbacks[0].proc’)
cyrus-sasl.c:113:29: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int,  const char **, unsigned int *)’ [-Wincompatible-pointer-types]
  113 |         { SASL_CB_AUTHNAME, &getuser_func, NULL },
      |                             ^
cyrus-sasl.c:113:29: note: (near initialization for ‘callbacks[1].proc’)
cyrus-sasl.c:114:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(sasl_conn_t *, void *, int,  sasl_secret_t **)’ {aka ‘int (*)(struct sasl_conn *, void *, int,  struct sasl_secret **)’} [-Wincompatible-pointer-types]
  114 |         { SASL_CB_PASS, &getpass_func, NULL },
      |                         ^
cyrus-sasl.c:114:25: note: (near initialization for ‘callbacks[2].proc’)
cyrus-sasl.c:119:24: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int,  const char *)’ [-Wincompatible-pointer-types]
  119 |         { SASL_CB_LOG, &sasl_log_func, NULL },
      |                        ^
cyrus-sasl.c:119:24: note: (near initialization for ‘debug_callbacks[0].proc’)
cyrus-sasl.c:120:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int,  const char **, unsigned int *)’ [-Wincompatible-pointer-types]
  120 |         { SASL_CB_USER, &getuser_func, NULL },
      |                         ^
cyrus-sasl.c:120:25: note: (near initialization for ‘debug_callbacks[1].proc’)
cyrus-sasl.c:121:29: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(void *, int,  const char **, unsigned int *)’ [-Wincompatible-pointer-types]
  121 |         { SASL_CB_AUTHNAME, &getuser_func, NULL },
      |                             ^
cyrus-sasl.c:121:29: note: (near initialization for ‘debug_callbacks[2].proc’)
cyrus-sasl.c:122:25: error: initialization of ‘int (*)(void)’ from incompatible pointer type ‘int (*)(sasl_conn_t *, void *, int,  sasl_secret_t **)’ {aka ‘int (*)(struct sasl_conn *, void *, int,  struct sasl_secret **)’} [-Wincompatible-pointer-types]
  122 |         { SASL_CB_PASS, &getpass_func, NULL },
      |                         ^
cyrus-sasl.c:122:25: note: (near initialization for ‘debug_callbacks[3].proc’)
strip --strip-debug lookup_program.so

(...)

make[1]: *** [Makefile:137: cyrus-sasl.o] Error 1
make[1]: *** Waiting for unfinished jobs....
strip --strip-debug lookup_yp.so
strip --strip-debug lookup_sss.so
strip --strip-debug lookup_file.so
strip --strip-debug parse_sun.so
strip --strip-debug mount_nfs.so
strip --strip-debug parse_amd.so
make[1]: Leaving directory '/home/ricardo/.cache/yay/autofs/src/autofs-5.1.9/modules'
make: *** [Makefile:14: daemon] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: autofs-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
autofs - exit status 4

I originally thought this should be in the "extra" repository.

7thSon - you need to install base-devel group if you want to build packages from AUR. This is listed in https://wiki.archlinux.org/title/Arch_User_Repository article.

I'm getting a build error with the latest version (5.1.8):

checking for lex... no
configure: error: required program LEX not found
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: autofs

Is this a known issue?

Thanks @Scottaroo! I incorporated your fix and pushed as update.

Sorry. Two lines:

sed -i -e "/^#include <linux\/fs.h>$/d" modules/parse_amd.c

sed -i -e "/^#include <linux\/fs.h>$/d" modules/parse_sun.c

Greetings:

While you are correct that recent changes with glibc have caused this to stop building and that it isn't autofs' fault, it's not a mistake or bug on glibc's part. They have made this change and they are ignoring people complaining about it. They expect people to update their code and live with it.

Commenting out "wrong" includes will fix the problem. In prepare(), you just need:

sed -i -e "/^#include <linux\/fs.h>$/d" modules/parse_amd.c sed -i -e "/^#include <linux\/fs.h>$/d" modules/parse_sun.c

and the package will build again.

Recently installed glibc and linux-api-headers have a conflict: /usr/include/sys/mount.h (from glibc) and /usr/include/linux/mount.h (from linux-api-headers). This is not autofs' fault.

I'm getting build error, It seems to be a problem with glibc 1.36?

/usr/include/linux/mount.h:95:6: error: redeclaration of ‘enum fsconfig_command’ 95 | enum fsconfig_command { | ^~~~~~~~~~~~~~~~