similar to: feedback on rsync-HEAD-20050125-1221GMT

I am trying to compile rsync-2.6.0 on BSD/OS 5.0 patched to current level. gcc version 2.95.3 I ran configure: ./configure --with-rsh=rsh This is the only error message given by configure: checking sys/sysctl.h usability... no checking sys/sysctl.h presence... yes configure: WARNING: sys/sysctl.h: present but cannot be compiled configure: WARNING: sys/sysctl.h: check for missing prerequisite

While building rsync 2.6.2 on my x86 Linux system using gcc 3.3.3, I observed a number of warnings from popt.c/h about ignoring qualifiers on return types. On further investigation, it looks like a few functions are declaring their return types as "const char * const". The first const is appropriate ("the chars pointed to by this pointer are const"), but the second is bogus

The following popt files need patches in order to compile using Compaq C on OpenVMS. These patches should also be needed on a Tru64 or LINUX on ALPHA using Compaq C. Except for the alloca issue, these should work on any ANSI compliant compiler. Operating System: OpenVMS ALPHA V7.3 Compiler: Compaq C T6.5 Compiler switches: /WARN=ENABLE=(LEVEL4, QUESTCODE) SYSTEM.H is doing tests on

Hi, Ever since after 2.5.1, rsync is no longer compiling cleanly, or make testing correctly : gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c log.c -o log.o log.c: In function `log_transfer': log.c:574: warning: unused parameter `file' gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c options.c -o options.o options.c:273: warning: missing initializer for

There are quite a few compilation warnings from rsync-2.5.5rc1 that could be eliminated by code cleanup. gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c main.c -o main.o main.c: In function `start_client': main.c:665: warning: unused variable `write_batch' main.c:664: warning: unused variable `whole_file' These warnings will go away when the two variables are properly bracketed

2.5.6pre1 bombs on Sunos4 gcc with these errors popt/popthelp.c: In function `singleOptionDefaultValue': popt/popthelp.c:137: invalid operands to binary + popt/popthelp.c:141: invalid operands to binary + popt/popthelp.c:145: invalid operands to binary + popt/popthelp.c:149: invalid operands to binary + because it's depending on sprintf to return the number of bytes

Folks, Just downloaded 2.5.2 to play with...builds with a raft of warnings, and the symlink test fails. Transcript below for anyone with the knowledge and energy to repair. This is done with gcc-3.0.3. David. ----- BUILD: corona 2.5.2 7 $ make gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c rsync.c -o rsync.o gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c generator.c -o

This is to let you know that although rsync compiled on MacOSX 10.2.2, it failed certain tests. I have attached two files: (1) The combined output of "./configure" and make", and (2) the output of "make check". Please let me know if you need any further information. Ed ------------------------------------------------------- Edward N. Zalta

When I compile on Solaris * I get the foillowing errors: bash-2.03# gmake gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c rsync.c -o rsync.o gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c generator.c -o generator.o gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c receiver.c -o receiver.o gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -c cleanup.c -o cleanup.o gcc

I'm having serious problems with the current 2.5.3 release under Debian "testing" and the 2.4.19-pre2 Linux kernel. As you can see from the appended build log, I get many compiler warnings. More seriously, when I install and try to use the resulting binaries over ssh, things bomb horribly, e,g: bash-2.05a$ rsync -vaz homer-rr.ka9q.net:wwv_wwvh . receiving file list ... done

I just picked up rsync 2.5.6 and installed it. I haven't actually _used_ it for anything yet; this is entirely about a handful of minor issues I noticed while building it. You may care or you may not; for simplicity of language (to avoid many repeated "in case you care" and such), the text below is written assuming you care about them all. On a (32-bit) SPARC system, I noticed:

Hi, everybody here! I hope not all is old stuff, because I only scanning subjects fast in this list. (and sorry for my worse english, too.) 1) rsync 2.6.0 on HP-UX (HP-UX server B.11.00 U 9000/803) Running as server: crashed always after receiving data. The data is transmitted correctly, and the server dies afterwards. (rsync2.5.7 works anyway) (about rsync2.6.2 later) 2) compiling

All seems to compile ok but I get the following warnings on interix 3.5 flist.c: In function `recv_file_entry': flist.c:840: warning: comparison between signed and unsigned flist.c:874: warning: comparison between signed and unsigned flist.c:876: warning: right shift count >= width of type flist.c: In function `make_file': flist.c:1178: warning: comparison between signed and unsigned

I am an rsync newbie trying to setup rsync on a HP UX 11.0 server, but am running into problems in my "make". I am using gcc version 3.3.2 and rsync-2.6.6.tar.gz. Would any of you have ideas on troubleshooting this issue? I haven't had much luck googling info on this, with the exception of switching from HP's simple c compiler to gcc. The warnings and errors I am recieving

I've added the: /etc/services /etc/inetd entries as well as /etc/rsync.conf with the contents: [io] path = //Volumes/Mac_OS_X/Library/WebServer/iolanguage.com/Io comment = iolanguage source code But I get this error: % rsync -rvR --progress localhost:/ . localhost.dekorte.com: Connection refused rsync: connection unexpectedly closed (0 bytes read so far) rsync error:

Hi: After compiling rsync2.5.6 using on SVR4 on Intel HW, Please help # ./rsync --version rsync: --version: unknown option rsync error: syntax or usage error (code 1) at main.c(994) # ./rsync --help Segmentation Fault - core dumped Here is log of compilation. Script started on Sat Jun 21 05:56:15 2003 # make cc -I. -I. -g -DHAVE_CONFIG_H -I./popt -c rsync.c -o rsync.o NCR High

Hi to all, On Solaris 9 (and below I think), Samba 3.0.1pre1's tdbbackup now needs snprintf which is not included in Solaris. The following patch on master Makefile.in (~samba/source) should ease the compilation of tdbbackup : diff -u Makefile.in.orig Makefile.in --- Makefile.in.orig Mon Oct 20 11:06:54 2003 +++ Makefile.in Mon Oct 20 11:07:09 2003 @@ -629,7 +629,7 @@

Did anyone have any luck compiling rsync 2.5.2, from source, on Mac OS X? Doing a straight ./configure && make, I get the error below. I've searched the lists here with no luck. Any pointers, or any URL with more info would be great. Thanks! RSYNC 2.5.2 COMPILING ERROR ON MAC OS X: root# make Please ignore warnings below about mktemp -- it is used in a safe way cc -g -O2

Dear all During compilation samba-3.0.21c on a HP-UX 11i v1 system I get an error. ./configure --prefix=/opt/samba-3.0.21c make ... Compiling popt/poptconfig.c Compiling popt/popthelp.c Compiling popt/poptparse.c Linking bin/smbd /usr/ccs/bin/ld: Unsatisfied symbols: auth_script_init (first referenced in auth/auth.o) (code) collect2: ld returned 1 exit status *** Error exit code 1 Can

Does anyone know why I cannot compile the 3.0.0 release of Samba on Compaq Tru64 4.0f (aka DEC OSF1 version 4.0f) I have read the mailing list quite a lot and have done the chmod adjustment to the "install-sh" file, and then ran "./configure" I am not using gcc nor am I using GNU make, I am using the default compiler and make supplied with the OS. the "./configure"