similar to: Long-pending patch for Stratus VOS build

This is an updated version of my patches to get rsync to build and run its tests on the Stratus VOS operating system. I have updated this patch to apply cleanly to the current copy of HEAD. I also ran the test suite and discovered that I needed to tweak a few spots in the Makefile to append the executable suffix (VOS is one of the few systems that has a required executable suffix). There are a

This is a corrected version of the patch I originally submitted on September 5th, and resubmitted on October 14th. I have removed the changes that added $(CFLAGS) to the link-only invocations of gcc. Otherwise, the patch is the same as before. My thanks to Paul (prj@po.cwru.edu) for noticing my error and kindly correcting me. ** text of original letter, with corrections ** I had to make some

I had to make some patches to rsync to get it to build on VOS. We are a POSIX-96 (but not Unix) system. Here is the subset of the patches that I think are general to all platforms. I have tested these here. I was surprised that CPPFLAGS is not available to the compilation rules in the Makefile. Most other packages (e.g. Samba) seem to allow CPPFLAGS to be set by the user. Since this is how I

** This is a resend of mail I originally sent on September 5th. I am still interested in getting these patches applied, and getting a new config.guess and config.sub. Is there anything else I need to do in order to get these changes accepted? Thanks. PG ** I had to make some patches to rsync to get it to build on VOS. We are a POSIX-96 (but not Unix) system.

For those interested : My port of Samba 1.9.17p4 to STRATUS VOS is now available on ftp://ftp.stratus.com/pub/vos/tools Erik 'Samba for VOS' Devriendt

Ville Herva [mailto:vherva@niksula.hut.fi] wrote: > Of course, whether O_TEXT is defined or not does not > necessarily imply the availability of "t", but I > can't think of better alternative. Stratus VOS implements O_TEXT and O_BINARY but does not recognize "t". We have the options defined in ANS C and in POSIX. I'm at home and don't have my reference

I am guessing that since the error is on the first instance of the use of foo$(VAR): foo.o construct, that the Irix makefile parser doesn't know how to deal with this line. Obviously they don't use GNU make.... So here is a patch to Makefile.in that simplifies the use of variables. This only uses constructs that should work in all makes. It should not break anything, and it

Sviatoslav Sviridov [mailto:svd@ns1.lintec.minsk.by] wrote: >It would be good if attached patch will be included in upstream. This >patch adds option --apt-support for rsync and with this option rsync >will print some additional information about file being transfered. No >program logic changed. Having this option in rsync we can have apt with >rsync method support. 1. What is apt?

I tend to be someone who automatically looks for trends, and the nice thing about having just one list is that it lets me know where people are having problems. Judging by the number of questions we get, one of the biggest challenges for inexperienced rsync users is knowing why a particular file is included or excluded. Way in the back of my mind I see a need for an option that, for every file

Steve Bonds [mailto:knnf6cy7w001@sneakemail.com] wrote: >I couldn't get the ssh tests to work in rsync 2.5.6 and it doesn't appear >that they ever could have worked. There were two problems with the script >I noticed: > >1) The "from" directory is never populated with files to test. It looked >like the "hands_setup" function from rsync.fns was

>jw schultz [mailto:jw@pegasys.ws] wrote: >On Fri, Feb 07, 2003 at 11:15:57AM -0500, Roderick Schertler wrote: >> Under Aix directories have the mode 024xxxx instead of the customary >> 04xxxx. Because of this when you sync a directory to or from an Aix >> system it's never up to date. >> >> Here is a patch which fixes this. It causes rsync to look at

On Fri, Jul 31, 2015 at 12:15 AM, Herbie Robinson <HerbieRobinson at verizon.net> wrote: > I have been quietly working on a port of LLVM to Stratus VOS. The OS is > always big endian (because customers need to migrate data to new hardware > quickly and can't afford to convert). This entails presenting a big endian > programming model no matter what the hardware does. We

Patches welcome, eh, Paul? Upon further (belated) investigation, there are 2 affected places in receiver.c with this error message. Both call write_file(). And write_file is called only in those two places. So that is the appropriate location to patch. Especially since the obvious fix is to use the rewrite code already there for the sparse file writes.

I'd like to suggest that this is now a great time to create two separate cvs branches for the rsync product. One, which I'll tentatively call 2_5, would hold the version of the code that has been released to the world as 2.5.6. The other, which I'll tentatively call head, would hold the development activity leading up to the next field release. I'm not bound to these names, but I

Is rsync under active maintenance and development? I ask because I have twice submitted a small set of patches to this mailing list and have never received any indication that the proposed patches were either applied or rejected. I notice that the rsync-cvs mailing archive shows that no patches have been applied to rsync in about 8 weeks. I tried sending a personal letter to two of the

I have been quietly working on a port of LLVM to Stratus VOS. The OS is always big endian (because customers need to migrate data to new hardware quickly and can't afford to convert). This entails presenting a big endian programming model no matter what the hardware does. We did this about 15 years ago with the Stratus compilers and GCC. We offered the GCC changes back to the

On Tue, Nov 05, 2002 at 08:37:00AM -0800, Martin Pool wrote: > On 10 Oct 2002, "Green, Paul" <Paul.Green@stratus.com> wrote: > > No new CVS messages have appeared on the rsync-cvs archives since August > > 30th. This seems rather odd-- perhaps a daemon stopped working? If there > > has truly been no activity since that date, I apologize for > >

http://bugzilla.mindrot.org/show_bug.cgi?id=978 Summary: The supplied realpath function mangles pathnames. Product: Portable OpenSSH Version: 3.9p1 Platform: Other OS/Version: other Status: NEW Severity: minor Priority: P3 Component: Miscellaneous AssignedTo: openssh-bugs at mindrot.org

> > I am looking for "how to" information / references on use of either Audiocodes MP104 or 108, or Vega 50 Gateways for interconecting Asterisk to the PSTN via FX0 interfaces. > > Any info of references / personnal experiences would be appreciated > > Stratus? THE WORLD'S MOST RELIABLE SERVERS * > Richard C. Sparacino > Telecom Technology Manager

<http://jbala.ws/lists/lt.php?id=MkxaBQUECR0FTgEDXVVW> -- Pour vous d?sabonner ? cette liste, visitez http://jbala.ws/lists/lt.php?id=MkxaBQUFAB0FTgEDXVVW Pour mettre vos pr?f?rences ? jour, visitez http://jbala.ws/lists/lt.php?id=MkxaBQUFAR0FTgEDXVVW Faire suivre un message a quelqun http://jbala.ws/lists/lt.php?id=MkxaBQUFAh0FTgEDXVVW -- Powered by PHPlist, www.phplist.com --