maybe it's a bug in the configure-script, but as soon as you specify --enable-ea-support *or* --disable-ea-support (doesn't matter), EA support will be disabled. If you specify nothing, it will be enabled. easy check: ./configure --enable-ea-support [..] LIBDAR parameters: Zlib compression (gzip) : YES Libbz2 compression (bzip2) : YES Strong encryption support : YES Extended Attributes support: NO Large files support (> 2GB): YES ext2fs NODUMP flag support : YES Special allocation scheme : YES Integer size used : infinint Thread safe support : YES and now w/o any options: ./configure [..] LIBDAR parameters: Zlib compression (gzip) : YES Libbz2 compression (bzip2) : YES Strong encryption support : YES Extended Attributes support: YES Large files support (> 2GB): YES ext2fs NODUMP flag support : YES Special allocation scheme : YES Integer size used : infinint Thread safe support : YES "./configure --help" say this: --disable-ea-support disable Extended Attributes support --disable-nodump-flag deactivate the "ext2/3 nodump flag" feature check so it seems, that you should not use --enable-* but --disable-* conclusion: use acl && myconf="${myconf} --enable-ea-support" is wrong and should be written as: use acl || myconf="${myconf} --disable-ea-support" should be easy to fix. Reproducible: Always Steps to Reproduce:
fixed in cvs. thanks.
