/usr/bin/dar -V Mageia 2: dar version 2.4.7, Copyright (C) 2002-2052 Denis Corbin Long options support : YES Using libdar 5.2.4 built with compilation time options: Libz compression (gzip) : YES Libbz2 compression (bzip2) : YES Liblzo2 compression (lzo) : YES Strong encryption : YES Extended Attributes support: YES Large files support (> 2GB): YES ext2fs NODUMP flag support : NO Special allocation scheme : YES Integer size used : unlimited Thread safe support : YES Furtive read mode support : YES Detected system/CPU endian : little Large dir. speed optimi. : YES compiled the Aug 29 2012 with GNUC version 4.6.3 dar is part of the Disk ARchive suite (Release 2.4.7) dar comes with ABSOLUTELY NO WARRANTY; for details type `dar -W'. This is free software, and you are welcome to redistribute it under certain conditions; type `dar -L | more' for details. Mageia 3: dar version 2.4.2, Copyright (C) 2002-2052 Denis Corbin Long options support : YES Using libdar 5.1.1 built with compilation time options: Libz compression (gzip) : YES Libbz2 compression (bzip2) : YES Liblzo2 compression (lzo) : NO Strong encryption : NO Extended Attributes support: YES Large files support (> 2GB): YES ext2fs NODUMP flag support : YES Special allocation scheme : YES Integer size used : unlimited Thread safe support : YES Furtive read mode support : YES Detected system/CPU endian : little compiled the Jan 11 2013 with GNUC version 4.7.2 dar is part of the Disk ARchive suite (Release 2.4.2) dar comes with ABSOLUTELY NO WARRANTY; for details type `dar -W'. This is free software, and you are welcome to redistribute it under certain conditions; type `dar -L | more' for details. This prevents people from using backups that where created and compresses using dar on Mageia2. This looks like a missing buildrequires for liblzo-devel Strong encryption should also be enabled.
Source RPM: (none) => dar-2.4.2-3.mga3.src.rpm
for strong encryption: Buildrequires libgcrypt-devel however, if this library is installed, the dar static component won't build. BUILD/dar-2.4.2 -------------------------- Error: grep -e -static -A 2 config.log configure:11208: checking if gcc static flag -static works configure:11236: result: yes configure:11246: checking if gcc supports -c -o file.o -- configure:16057: checking if g++ static flag -static works configure:16085: result: yes configure:16095: checking if g++ supports -c -o file.o -- configure:31798: g++ -o conftest -O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fPIC -static conftest.cpp -lpthread -lattr -lgcrypt -lgpg-error -llzo2 -lbz2 -lz -ldl >&5 /usr/bin/ld: cannot find -lgcrypt /usr/bin/ld: cannot find -lgpg-error ------------------------------ /SPECS/log.dar dar and libdar have been successfully configured with the following parameters: LIBDAR parameters: Zlib compression (gzip) : YES Libbz2 compression (bzip2) : YES Liblzo2 compression (lzo) : 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 Furtive read mode : YES DAR SUITE command line programs: Long options available : YES Building examples : NO Building dar_static : NO (system does not support static linking, see note below) using upx at install : NO building documentation : YES Note: If you want to know which libraries are not available as static libraries check the logs in the config.log generated file. the command 'grep -e -static -A 2 config.log' should bring you to the essentials. You also might want to speed up the compilation process running ./configure with the --disable-shared option
I've updated dar to latest version, updated missing BRs and disabled the static build as we don't have all required static devel pkgs to build static version anymore.
CC: (none) => jani.valimaa
(In reply to Jani Välimaa from comment #2) > I've updated dar to latest version, updated missing BRs and disabled the > static build as we don't have all required static devel pkgs to build static > version anymore. Of course this is for Cauldron. Have to check mga3 build later.
Btw, mga2 and mga3 ships with dar 2.4.2. Your paste shows you have 2.4.7 in mga2, so it's not from official repos. Only thing mga3 dar differs with one from mga2 is "ext2fs NODUMP flag support". It's disabled in mga2, but enabled in mga3. So there's no real regression between official releases.
Sorry, maybe I had recompiled dar on Mageia 2 and forgotten that I had. Thank you for adding the build requires. I've been using the 2.4.7 on my Mageia 2 instance for some time, it proved stable. I see that current release is 2.4.10.. So if cauldron can go to that it would be nice. How difficult is it to build the needed static lib, so that dar can be compiled static? I am not sure, but is it just gcrypt and gpg that we would need static dev libs for? I can see the occasional use case for the static version, where people are wanting to do a system restore.
Keywords: (none) => TriagedAssignee: bugsquad => bruno
Upstream is now 2.4.11. I've updated dar to this version and will ask t to pushed into mga4 to close this bug.
Status: NEW => ASSIGNED
mga4 has it. Can we close it ?
Fixed IMO now.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED