[GH-ISSUE #1926] S3FS fails to build on Debian 11 bullseye (`line 4984: PKG_CHECK_MODULES`) #968

New issue

Closed

opened 2026-03-04 01:50:18 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:50:18 +03:00

Owner

Originally created by @bryanpedini on GitHub (Mar 18, 2022).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1926

Additional Information

Version of s3fs being used (s3fs --version)

s3fs-fuse-1.91 from GitHub releases

Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)

2.9.9-5

Kernel information (uname -r)

uname -r

5.10.0-12-amd64

GNU/Linux Distribution, if applicable (cat /etc/os-release)

/etc/os-release

PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

s3fs command line used, if applicable

N/A

/etc/fstab entry, if applicable

N/A

s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)

N/A

Details about issue

I'm trying to build S3FS for Debian 11 (Proxmox Backup Server) tho command ./configure --prefix=/usr --with-openssl fails at line 4984 at PKG_CHECK_MODULES check:

Output

checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking sys/xattr.h usability... yes
checking sys/xattr.h presence... yes
checking for sys/xattr.h... yes
checking attr/xattr.h usability... no
checking attr/xattr.h presence... no
checking for attr/xattr.h... no
checking sys/extattr.h usability... no
checking sys/extattr.h presence... no
checking for sys/extattr.h... no
checking for fallocate... yes
checking s3fs build with nettle(GnuTLS)... no
checking s3fs build with OpenSSL... yes
checking s3fs build with GnuTLS... no
checking s3fs build with NSS... no
./configure: line 4984: syntax error near unexpected token `common_lib_checking,'
./configure: line 4984: `PKG_CHECK_MODULES(common_lib_checking, fuse >= ${min_fuse_version} libcurl >= 7.0 libxml-2.0 >= 2.6 )'

Packages installed to build

build-essential
libfuse-dev
libcurl4-openssl-dev
libxml2-dev
mime-support
automake
libtool

libssl-dev libcurl4-openssl-dev
libxml2 libxml2-dev
libxml++2.6-2v5
libxml++2.6-dev
fuse
dpkg-dev
devscripts

To be noted: the first group is what I installed from the Wiki, the second group was based on maresb/docker-build-s3fs project, that's why the duplicate packages and the manually installed packages contained in other later-installed metapackages.

Originally created by @bryanpedini on GitHub (Mar 18, 2022). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1926 ## Additional Information #### Version of s3fs being used (s3fs --version) s3fs-fuse-1.91 from GitHub releases #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) 2.9.9-5 #### Kernel information (uname -r) <details> <summary>uname -r</summary> ``` 5.10.0-12-amd64 ``` </details> #### GNU/Linux Distribution, if applicable (cat /etc/os-release) <details> <summary>/etc/os-release</summary> ``` PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" ``` </details> #### s3fs command line used, if applicable N/A #### /etc/fstab entry, if applicable N/A #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) N/A ### Details about issue I'm trying to build S3FS for Debian 11 (Proxmox Backup Server) tho command `./configure --prefix=/usr --with-openssl` fails at line 4984 at `PKG_CHECK_MODULES` check: <details> <summary>Output</summary> ``` checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking target system type... x86_64-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for g++... g++ checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking whether make supports the include directive... yes (GNU style) checking dependency style of g++... gcc3 checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking sys/xattr.h usability... yes checking sys/xattr.h presence... yes checking for sys/xattr.h... yes checking attr/xattr.h usability... no checking attr/xattr.h presence... no checking for attr/xattr.h... no checking sys/extattr.h usability... no checking sys/extattr.h presence... no checking for sys/extattr.h... no checking for fallocate... yes checking s3fs build with nettle(GnuTLS)... no checking s3fs build with OpenSSL... yes checking s3fs build with GnuTLS... no checking s3fs build with NSS... no ./configure: line 4984: syntax error near unexpected token `common_lib_checking,' ./configure: line 4984: `PKG_CHECK_MODULES(common_lib_checking, fuse >= ${min_fuse_version} libcurl >= 7.0 libxml-2.0 >= 2.6 )' ``` </details> <details> <summary>Packages installed to build</summary> ``` build-essential libfuse-dev libcurl4-openssl-dev libxml2-dev mime-support automake libtool libssl-dev libcurl4-openssl-dev libxml2 libxml2-dev libxml++2.6-2v5 libxml++2.6-dev fuse dpkg-dev devscripts ``` To be noted: the first group is what I installed from the Wiki, the second group was based on [maresb/docker-build-s3fs](https://github.com/maresb/docker-build-s3fs/blob/master/dockerfile_scripts/010-install-build-tools.sh) project, that's why the duplicate packages and the manually installed packages contained in other later-installed metapackages. </details>

kerem closed this issue

2026-03-04 01:50:18 +03:00

kerem commented

2026-03-04 01:50:19 +03:00

Author

Owner

@AlexFromXD commented on GitHub (Dec 7, 2022):

I follow this instruction and it works

@AlexFromXD commented on GitHub (Dec 7, 2022): I follow this [instruction](https://github.com/s3fs-fuse/s3fs-fuse/wiki/Installation-Notes#debian--ubuntu) and it works

kerem commented

2026-03-04 01:50:19 +03:00

Author

Owner

@ggtakec commented on GitHub (Jan 11, 2023):

@bryanpedini I'm sorry for my late reply.
After merging #1842 the code should now build on Debian 11.

@ggtakec commented on GitHub (Jan 11, 2023): @bryanpedini I'm sorry for my late reply. After merging #1842 the code should now build on Debian 11.