similar to: rsync 2.6.2: clean up compilation warnings

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

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

Wayne, I have been using the rsync snapshot from 1/25 for the last few days and everything seems quite solid so far. I include below a few nit-picks in case you're looking for thing to tidy up. I'm also looking forward to hearing news about the --filter option. I'm thinking it is going to be very useful for backup purposes. What I would want to be able to do is, on a

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

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, 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

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

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

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

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

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

Dear Customer! This is an automatic response from our support system, because you have sent a message to our support system e-mail address, which does not refer to an existing support case tracking number. We regret to inform you that we can no longer process such messages and your e-mail has, therefore, NOT been delivered. We have recently implemented a new support case management system in

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

--==M2004020923123623794 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --- The message cannot be delivered to the following address. --- anna@metso.com Permanent error involving remote host. 554 Transaction failed (too many hops) --==M2004020923123623794 Content-Type: message/delivery-status Reporting-MTA: mailgate01@metso.com Final-Recipient:

Hi, Have anybody recently built LLVM in Debug mode /within/ space requirements from the Getting Started doc? https://llvm.org/docs/GettingStarted.html#hardware > An LLVM-only build will need about 1-3 GB of space. A full build of LLVM and Clang will need around 15-20 GB of disk space. From my experience this numbers looks drastically low. On FreeBSD my recent builds consumed more than

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:

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

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 @@