Hello Group,
Sorry if this is an off-topic question for rdiff-backup. I had problem
installing librsync on a 64-bit server. My rdiff-backup process runs
smoothly on 32-bit workstation.
Here is the error during the installation:
gcc -Wall -Wshadow -Wundef -Wwrite-strings -Wmissing-prototypes -
RudySC wrote:
/usr/lib/libpopt.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
make[2]: *** [rdiff] Error 1
make[2]: Leaving directory `/usr/local/src/librsync-0.9.7'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
I already had the 64-bit libsrync. But I had a new problem installing
the rdiff app itself. Here's the error I encountered:
python setup.py install
running install
running build
running build_py
running build_ext
building 'rdiff_backup._librsync' extension
gcc -pthread -shared
Hi,
it seems to me another way to run rdiff-backup on a Windows XP SP2 machine:
Installing SFU 3.5, installing librsync with all the terrible
dependencies, installing python and compiling the stuff.
But the compiler gives up as follows:
% python setup.py
RudySC wrote:
I already had the 64-bit libsrync. But I had a new problem installing
the rdiff app itself. Here's the error I encountered:
python setup.py install
running install
running build
running build_py
running build_ext
building 'rdiff_backup._librsync' extension
gcc -pthread
Ralph Lehmann wrote:
error: command 'gcc' terminated by signal 11
If it's referring to Unix signal 11 (SIGSEGV) then there's probably
something wrong with your system. If we knew everything worked, then it
could be bad RAM. But in this case, it's probably something wrong with
gcc or your
Andrew Ferguson schrieb:
Ralph Lehmann wrote:
error: command 'gcc' terminated by signal 11
If it's referring to Unix signal 11 (SIGSEGV) then there's probably
something wrong with your system.
Turning off data execution prevention works around _this_ problem.
Thank you! :-)
ciao Ralph
Andrew Ferguson schrieb:
Ralph Lehmann wrote:
error: command 'gcc' terminated by signal 11
If it's referring to Unix signal 11 (SIGSEGV) then there's probably
something wrong with your system.
This problem is solved now. But another attempt th install rdiff-backup
fails with:
Hi All,
I love rdiff-backup. However, I don't like how fragile it is when it
crashes during a backup. Let's say the client pushes some backup data to a
remote server, but in the middle of a file transfer, the remote server's
network goes out. The next time rdiff-backup is executed, it
Related to the recent post on how to recover from a crash during a
backup, here's a question that has been on my mind lately. Is there any
way to make rdiff-backup more robust so that it doesn't crash during a
backup? I've been trying to get it to work with an SMB-mounted
filesystem, and every
Is it possible to build SafeKeep around a newer (development) version of
rdiff-backup? Put another way, will SafeKeep use the installed version
of rdiff-backup, or is rdiff-backup rolled into the code? Until the
latest unstable version, rdiff-backup didn't work well with SMB
filesystems, so
On Mon, 2007-06-25 at 23:40 -0400, Eric Jensen wrote:
Is it possible to build SafeKeep around a newer (development) version
of rdiff-backup? Put another way, will SafeKeep use the installed
version of rdiff-backup, or is rdiff-backup rolled into the code?
Yes, SafeKeep will use the
12 matches
Mail list logo
