windows compilation problem

2011-06-24 Thread FELLIN, JEFFREY K (JEFF)
I'm compiling rsync 3.0.9pre1 using Microsoft Visual Studio 2010 on my windows XP system. I get a compilation failure in flist.c, function send_directory: flist.c(1653) : error C2143: syntax error : missing ';' before 'type' flist.c(1654) : error C2065: 'name_len' : undeclared identifier

Re: Compilation problem with linux/falloc.h include in rsync.h

2011-05-16 Thread Wayne Davison
On Sun, May 15, 2011 at 9:36 AM, Mulander netpr...@gmail.com wrote:  #if defined HAVE_FALLOCATE || HAVE_SYS_FALLOCATE -#include linux/falloc.h +#include fcntl.h  #ifdef FALLOC_FL_KEEP_SIZE Rsync already includes fcntl.h higher up in rsync.h. The problematical include is to try to get

Compilation problem with linux/falloc.h include in rsync.h

2011-05-15 Thread Mulander
=28b519c93b6db30b6520d46f8cd65160213fddd2 Since the change is quite fresh (2011-04-05) I was thinking that this is a possible configuration/conditional compilation problem. I'm just starting to learn the rsync code base and I am not sure how this issue should be correctly handled hence my email to this mailing list in the hope

Re: Compilation problem with linux/falloc.h include in rsync.h

2011-05-15 Thread Mulander
Here is the diff I applied to my copy of the sources which allowed me to pass the compilation without any problems. Just for the record I'm testing this on Slackware GNU/Linux: mulander@bunkier_mysli:~/code/blog/lac/rsync$ uname -a Linux bunkier_mysli 2.6.32.7-grsec #2 SMP Sat Feb 6 11:22:33 CET

Re: Rsync cross-compilation problem

2005-01-24 Thread Wayne Davison
On Mon, Jan 24, 2005 at 01:07:28AM -0600, John Van Essen wrote: shouldn't the compiler abort with a meaningful error message in the #else of the #if sequence? The idea is to still allow rsync to run with 32-bit offsets if the maximum filesize for a system fits in 32 bits. I haven't seen

Re: Rsync cross-compilation problem

2005-01-24 Thread Florian Fainelli
Hi all, Thanks a lot for your help, when defining LONGLON, it works like a charm. I just cached the value rsync_ac_cv_HAVE_LONGLONG=yes before running the configure script. Instead of having rsync_ac_cv_HAVE_LONGLONG=cross. Thanks for your help, good luck for your wonderful project ! Best

Re: Rsync cross-compilation problem

2005-01-23 Thread John Van Essen
On Thu, 20 Jan 2005, Wayne Davison [EMAIL PROTECTED] wrote: On Thu, Jan 20, 2005 at 01:54:20AM -0600, John Van Essen wrote: (Note to Wayne - isn't it dangerous to assume that off_t is 64 bits? Yeah, it probably is -- that code was always a kluge that doesn't really get used. I looked around

Re: Rsync cross-compilation problem

2005-01-20 Thread Wayne Davison
On Thu, Jan 20, 2005 at 01:54:20AM -0600, John Van Essen wrote: (Note to Wayne - isn't it dangerous to assume that off_t is 64 bits? Yeah, it probably is -- that code was always a kluge that doesn't really get used. I looked around at the rest of the rsync code, and it looks to me like the

Rsync cross-compilation problem

2005-01-19 Thread Florian Fainelli
Hi all ! I really appreciate rsync, so that I would like to make a package for the mips architecture, but I encounter a problem when trying to cross compile it : the configure script has been called using the following options : --with-gnu-ld \ --disable-largefiles \ --with-included-popt

Re: Rsync cross-compilation problem

2005-01-19 Thread John Van Essen
On Wed, 19 Jan 2005, Florian Fainelli [EMAIL PROTECTED] wrote: And when using the cross compiler, I get the following message : In file included from rsync.c:23: rsync.h:360: warning: no semicolon at end of struct or union rsync.h:360: error: parse error before inode rsync.h:361: error:

compilation problem

2004-01-16 Thread Vlady
Hello, I have a RedHat 7.3 on which I deinstall the openssl-0.9.6b-35.7 and the openssl-devel-0.9.6b-35.7 packages and compiledinstall openssl-0.9.7c-1. After I downloaded, compiled install rsync-2.6.0 successfully exept that when I try to use I get the error: OpenSSL version mismatch. Built

Re: compilation problem

2004-01-16 Thread Wayne Davison
On Fri, Jan 16, 2004 at 12:23:56PM -0500, Vlady wrote: OpenSSL version mismatch. Built against 90602f, you have 90703f Rsync doesn't do anything directly with ssl, it runs the ssh program (by default in 2.6.0). You should ensure that you can ssh successfully into the system you want to rsync

Re: Compilation problem and solution on Solaris 2.7

2002-05-01 Thread Dave Dykstra
I compiled rsync 2.5.5 on Solaris 2.7 with both gcc and cc and did not get any errors about missing functions. Could you send me the output of configure? - Dave Dykstra On Sat, Apr 06, 2002 at 10:59:53AM +0200, Jean-Francois Stenuit wrote: To whoever it may help, My flavor of Solaris 2.7

Compilation problem and solution on Solaris 2.7

2002-04-06 Thread Jean-Francois Stenuit
To whoever it may help, My flavor of Solaris 2.7 was not able to compile rsync 2.5.5 with the vanilla ./configure; make. Three functions where missing : inet_ntop, inet_pton, inet_addr There are replacement inet_ntop and inet_pton in the distribution tree, so it's easy to change the Makefile