rodney at interopsystems.com
Thu Feb 12 16:35:48 GMT 2004
For compiling anything on Interix (SFU) you should set the
The latter two will cause "configure" to pick up any post installed libraries
and headers (not that they are needed in this case). The "-D_ALL_SOURCE"
opens up the guards in the header files for prototypes (since Interix is
being SUS compliant).
Changes I did to rsync were just for references to the "root" uid of 0 (zero).
I replaced all references of uid comparisons to 0 with a macro (ROOT_UID)
and then made a conditional define for ROOT_UID to be 0 when not Interix
and when Interix to be 197108 (local administrator which is the "root"
> Hi Dmitry,
> I've not had time to test it under SFU 3.5 - job for next week !
> I tried to compile rsync under SFU 3.5 .. and got into a world of pain
> with header files...
> But then Rodney at Interop systems did it for me..
> Although it's nice to have a static binary of rsync, having been reading
> the rsync mailing list the last few weeks now, it would seem that it
> would be better to compile rsync from source as it develops. I had no
> idea it was so actively under development !
> So, could you please detail the steps you took to sucessfully compile
> rsync under SFU 3.5 ??
> -----Original Message-----
> From: rsync-bounces+dkruse=staff.chariot.net.au at lists.samba.org
> [mailto:rsync-bounces+dkruse=staff.chariot.net.au at lists.samba.org] On
> Behalf Of Dmitry Melekhov
> Sent: Wednesday, 11 February 2004 11:26 PM
> To: rsync at lists.samba.org
> Subject: SFU?
> I just compiled rsync 2.6.0 on SFU 3.5 and it works :-)
> Did somebody test it for real work?
> Thank you!
More information about the rsync