On Sun, Oct 18, 2020 at 12:01 PM Craig Barratt via BackupPC-devel <
backuppc-devel@lists.sourceforge.net> wrote:
> Richard,
>
> Sorry about the delay in following up. rsync-bpc and rsync have very
> similar configuration scripts, and we need to find out why one fails but
> the other works. Both
Richard,
Sorry about the delay in following up. rsync-bpc and rsync have very
similar configuration scripts, and we need to find out why one fails but
the other works. Both detect that FALLOC_FL_PUNCH_HOLE is available, but
for some reason in rsync-bpc the reference to that macro fails.
It wou
Craig,
Any more input/advice on this?
Thanks,
Richard
>
___
BackupPC-devel mailing list
BackupPC-devel@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki:https://github.com/backuppc/backuppc/wiki
Project
On Mon, Oct 12, 2020 at 2:16 PM Craig Barratt via BackupPC-devel <
backuppc-devel@lists.sourceforge.net> wrote:
> What output do you get from:
>
> egrep FALLOC_FL_ config.h config.log
>
>
# egrep FALLOC_FL_ config.h config.log
config.h:/* Define if FALLOC_FL_PUNCH_HOLE is available. */
config.h:#d
What output do you get from:
egrep FALLOC_FL_ config.h config.log
Can you try building vanilla rsync-3.1.3 on that platform? The configure.ac
check for FALLOC_FL_PUNCH_HOLE should be the same as rsync-bpc-3.1.3.
Craig
On Mon, Oct 12, 2020 at 12:01 PM Richard Shaw wrote:
> Clicked send too s
Clicked send too soon...
This is with 3.1.3.0, 3.1.2.2 built fine.
gcc 4.4.7
Build log:
https://download.copr.fedorainfracloud.org/results/hobbes1069/BackupPC/epel-6-x86_64/01705128-rsync-bpc/build.log.gz
>
___
BackupPC-devel mailing list
BackupPC-dev
