similar to: rsync-2.5.1 / popt patches

The following zlib 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. 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) The module adler32.c is testing the unsigned value len to see if

In socket.c, the variable error is unitilialzed. Also the variable length should be an unsigned int. EAGLE> type socket.gdiff --- ref_src:socket.c Sat Jan 5 13:27:07 2002 +++ lcl_src:socket.c Sun Jan 6 08:40:51 2002 @@ -1,3 +1,4 @@ +/* Converted by prj_src:unix_c_to_vms_c.tpu AND prj_src:socket.tpu on 6-JAN-20 02 08:40:51.01 OPENVMS_AXP */ /* -*- c-file-style: "linux"

The following zlib files need patches in order to compile using Compaq C on OpenVMS. 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) fnmatch.c and mdfour.c. Compaq C on OpenVMS can not deal with relative path names in #include files. Also the local prototype for getenv() does

Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch is an update to a previous patch that I submitted. The only change from the previous patch is that the const qualifier has been added to write_batch_*() routines to improve compiler efficiency. Because the gdiff -u was done against the distribution it includes the previous patch. The functions with no parameters

Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch resolves compile problems with the checksum.c module. The type (char) was being used where the usage indicated either (void) or (unsigned char) should be used. The const qualifier was added to impove compiler efficiency. There may be more cases in this module where type (char) is being used instead of what appears

Platform: OpenVMS Alpha 7.3 Compiler: Compaq C T6.5-002 on OpenVMS Alpha V7.3 Comile flags: /WARN=ENABLE=(LEVEL4, QUESTCODE) Best guess at UNIX equivalents of above compile flags: LEVEL4 = All warnings QUESTCODE = Do LINT processing on source. -John wb8tyw@qsl.network Personal Opinion Only batch.c (char *) is being used as a type, when a generic structure is being passed. (void *) appears

Operating System: OpenVMS ALPHA V7.3 Compiler: Compaq C T6.5 Compiler switches: /WARN=ENABLE=(LEVEL4, QUESTCODE) syscall.c is missing the "const" qualifiers for several of it's functions. This patch should supercede the previous patch I submitted. This was discovered while working on resovling the conflicts between signed and unsigned values. -John wb8tyw@qsl.network Personal

Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch resolves compile problems with the IO.C module. The (char) type was being used where (void) was more appropriate based on the actual use of the code. The (char) type was also being used where the usage was actually an (unsigned char). const qualifiers were added to improve compile efficiency. EAGLE> type

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

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

Hello! I have any problem with construction (1-x)^(1-y) if y<1 > x=5 > y=.5 > (1-x)^(1-y) [1] NaN > (1-y) [1] 0.5 > (1-x)^0.5 [1] NaN > (1-x) [1] -4 > -4^.5 [1] -2 Roma V. Kalaida E-mail rss@rss.phtd.tpu.edu.ru <<insert bug report here>> --please do not edit the information below-- Version: platform = i686-pc-linux-gnu arch = i686 os = linux-gnu

Hi, I am having some issues with how some of the instructions are being legalized. So this is my intial basic block. The area of concern is the last three instructions. I will pick and choose debug output to keep this small. SelectionDAG has 36 nodes: t0: ch = EntryToken t6: i32,ch = CopyFromReg t0, Register:i32 %vreg507 t2: i32,ch = CopyFromReg t0, Register:i32 %vreg17

Hi. Here's a patch for copying the atimes of files when -t/--times is given. I bumped the protocol to 29 since it sends more data over the wire. It obviously does not send the atime if it's sending data to an older rsync version. It passes all the tests (including the added atime.test) for me on a: Linux Debian/3.0 gcc 2.95.4 (debian), glibc 2.2.5 system. Any questions/feedback? I

But isn't kinda silly that we transform to xor and then we transform it back. What is the advantage in doing so? Also, since we do that method, I now have to introduce setcc patterns for i1 values, instead of being able to just use logical pattern operators like not. -Dilan On Fri, Jul 21, 2017 at 11:00 AM Dilan Manatunga <manatunga at gmail.com> wrote: > For some reason I

I posted a patch a few days ago that adds copying of atime. At that time, it was just enabled with -t/--times. After some time, we have figured out that that choice might not have been the best. Here's a new version of the patch (relative to CVS) that adds -A/--copy-atime instead. It also includes a test case. Any feedback on this patch and/or the previous one that I posted?

Hi, Frequently when compiling rsync, I get this error during the make process: gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c options.c -o options.o options.c:24:18: popt.h: No such file or directory make: *** [options.o] Error 1 This is easily fixed by changing line 24 of options.c from: #include <popt.h> to #include "popt/popt.h" Thanks! -- Phil Hassey VP, Product

I am still chasing this down, but in doing the build for OpenVMS, I have discovered that one of the popt modules is using HAVE_ALLOCA_H to determine if the alloca function is on a platform. That is not a good assumption. Compaq C does have an alloca() built in (slightly different symbol name, I assume because of symbol naming rules in the C standard.) Because alloca is a non-standard

This patch updates the files under popt/ to the latest vendor drop. The only change is the inclusion of a FreeBSD-specific patch to popt.c. This is needed in case somebody decides to build rsync on that platform without using the port. I'm not happy about the wording in popt/README.rsync so I may change it. The patch is available at http://www.catnook.com/rsync-popt-1.5.1.patch Comments

http://www.catnook.com/patches/rsync-popt-1.6.4.patch has a patch which upgrades the popt included with rsync to the latest version, 1.6.4. The configure script had to be regenerated (with autoconf 2.53) because popt.c wants HAVE_FLOAT_H. As an aside, I have heard people complain about this version of autoconf generating scripts that break when run under bash (as /bin/sh). Comments? -- Jos

Perhaps now is a good time to commit this patch which updates the included popt to version 1.7. This has been tested on FreeBSD and Solaris. http://www.catnook.com/patches/rsync-popt-1.7.diff Comments? -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/