Re: Cannot build rsync 3.1.0 on MacOSX 10.8.5 with fileflags patch
Not trying to derail the tread here, but if you all like I can help you guys out in someway with testing on mac 10.8.5 if you like? On Sunday 27 October 2013 11:17:19 Wayne Davison wrote: On Thu, Oct 10, 2013 at 3:39 PM, Anthony Morton amor...@fastmail.fm wrote: However, attempting to build the new 3.1.0 release on a brand new Mountain Lion box with my standard 'fileflags' and 'crimes' patches applied, make fails, reporting that 'force_change' is undeclared. Yeah, the variable declaration got stuck in the wrong patch. I'm checking-in a fix for that in git. The OS X patches are not well tested at the moment. I managed to snag an old mac to do some build testing at least, but haven't done any testing other than making sure that it passed the make check tests (which I also fixed). ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Cannot build rsync 3.1.0 on MacOSX 10.8.5 with fileflags patch
On Thu, Oct 10, 2013 at 3:39 PM, Anthony Morton amor...@fastmail.fm wrote: However, attempting to build the new 3.1.0 release on a brand new Mountain Lion box with my standard 'fileflags' and 'crimes' patches applied, make fails, reporting that 'force_change' is undeclared. Yeah, the variable declaration got stuck in the wrong patch. I'm checking-in a fix for that in git. The OS X patches are not well tested at the moment. I managed to snag an old mac to do some build testing at least, but haven't done any testing other than making sure that it passed the make check tests (which I also fixed). ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync 3.1.0 failing [iobuf] on MacOSX 10.8.5 (was Re: Cannot build rsync 3.1.0 on MacOSX 10.8.5 with fileflags patch)
On Oct 12, 2013, at 12:36 AM, Anthony Morton amor...@fastmail.fm wrote: I got 3.1 to build all right on OS X but it won't run without stalling and lots of errors. Is it working for you or anyone else yet or have the problems come to light? Yes, now I'm using it in anger I'm seeing several fatal errors like the following (I'm syncing with a local mount point, no network access involved): need to write 129836 bytes, iobuf.out.buf is only 65532 bytes. rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0] rsync: [sender] write error: Broken pipe (32) Yes this is the error. I assume it has to do with the changes to the output buffer code in io.c 3.0.9 works great so I'm staying there for now and thankful for it. Would be nice if someone with a bit more rsync code experience could take a look too. Cheers, Rob need to write 401925 bytes, iobuf.out.buf is only 65532 bytes. rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0] rsync: [sender] write error: Broken pipe (32) I've rolled back to version 3.0.5 (the most recent I had installed previously) and it seems to be doing the job. Tony M. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync 3.1.0 failing [iobuf] on MacOSX 10.8.5 (was Re: Cannot build rsync 3.1.0 on MacOSX 10.8.5 with fileflags patch)
Hello, people. On 10/12/2013 02:56 PM, Robert DuToit wrote: On Oct 12, 2013, at 12:36 AM, Anthony Morton amor...@fastmail.fm wrote: I got 3.1 to build all right on OS X but it won't run without stalling and lots of errors. Is it working for you or anyone else yet or have the problems come to light? Yes, now I'm using it in anger I'm seeing several fatal errors like the following (I'm syncing with a local mount point, no network access involved): need to write 129836 bytes, iobuf.out.buf is only 65532 bytes. rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0] rsync: [sender] write error: Broken pipe (32) Yes this is the error. I assume it has to do with the changes to the output buffer code in io.c 3.0.9 works great so I'm staying there for now and thankful for it. Would be nice if someone with a bit more rsync code experience could take a look too. Yeah, I've seen that IO_BUFFER_SIZE was increased from 4092 to 32*1024 in version 3.1.0. However it works well on my Linux systems.. And I'm using it on my production servers already. Just a hypothesis, can you show ulimit -a? Cheers, Rob need to write 401925 bytes, iobuf.out.buf is only 65532 bytes. rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0] rsync: [sender] write error: Broken pipe (32) I've rolled back to version 3.0.5 (the most recent I had installed previously) and it seems to be doing the job. Tony M. -- С уважением, Дмитрий, начальник отдела UNIX-технологий, тел. 8 (495) 788-56-99, доб. 8255 signature.asc Description: OpenPGP digital signature -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync 3.1.0 failing [iobuf] on MacOSX 10.8.5 (was Re: Cannot build rsync 3.1.0 on MacOSX 10.8.5 with fileflags patch)
On Oct 12, 2013, at 7:11 AM, Dmitry Yu Okunev dyoku...@ut.mephi.ru wrote: Hello, people. On 10/12/2013 02:56 PM, Robert DuToit wrote: On Oct 12, 2013, at 12:36 AM, Anthony Morton amor...@fastmail.fm wrote: I got 3.1 to build all right on OS X but it won't run without stalling and lots of errors. Is it working for you or anyone else yet or have the problems come to light? Yes, now I'm using it in anger I'm seeing several fatal errors like the following (I'm syncing with a local mount point, no network access involved): need to write 129836 bytes, iobuf.out.buf is only 65532 bytes. rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0] rsync: [sender] write error: Broken pipe (32) Yes this is the error. I assume it has to do with the changes to the output buffer code in io.c 3.0.9 works great so I'm staying there for now and thankful for it. Would be nice if someone with a bit more rsync code experience could take a look too. Yeah, I've seen that IO_BUFFER_SIZE was increased from 4092 to 32*1024 in version 3.1.0. However it works well on my Linux systems.. And I'm using it on my production servers already. Just a hypothesis, can you show ulimit -a? it shows: core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 256 pipe size(512 bytes, -p) 1 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 709 virtual memory (kbytes, -v) unlimited Rob Cheers, Rob need to write 401925 bytes, iobuf.out.buf is only 65532 bytes. rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0] rsync: [sender] write error: Broken pipe (32) I've rolled back to version 3.0.5 (the most recent I had installed previously) and it seems to be doing the job. Tony M. -- С уважением, Дмитрий, начальник отдела UNIX-технологий, тел. 8 (495) 788-56-99, доб. 8255 -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Rsync 3.1.0 failing [iobuf] on MacOSX 10.8.5 (was Re: Cannot build rsync 3.1.0 on MacOSX 10.8.5 with fileflags patch)
On 10/12/2013 03:49 PM, Robert DuToit wrote: On Oct 12, 2013, at 7:11 AM, Dmitry Yu Okunev dyoku...@ut.mephi.ru wrote: Hello, people. On 10/12/2013 02:56 PM, Robert DuToit wrote: On Oct 12, 2013, at 12:36 AM, Anthony Morton amor...@fastmail.fm wrote: I got 3.1 to build all right on OS X but it won't run without stalling and lots of errors. Is it working for you or anyone else yet or have the problems come to light? Yes, now I'm using it in anger I'm seeing several fatal errors like the following (I'm syncing with a local mount point, no network access involved): need to write 129836 bytes, iobuf.out.buf is only 65532 bytes. rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0] rsync: [sender] write error: Broken pipe (32) Yes this is the error. I assume it has to do with the changes to the output buffer code in io.c 3.0.9 works great so I'm staying there for now and thankful for it. Would be nice if someone with a bit more rsync code experience could take a look too. Yeah, I've seen that IO_BUFFER_SIZE was increased from 4092 to 32*1024 in version 3.1.0. However it works well on my Linux systems.. And I'm using it on my production servers already. Just a hypothesis, can you show ulimit -a? it shows: core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited file size (blocks, -f) unlimited max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 256 pipe size(512 bytes, -p) 1 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 709 virtual memory (kbytes, -v) unlimited OK, the hypothesis was wrong. Sorry, :). Rob Cheers, Rob need to write 401925 bytes, iobuf.out.buf is only 65532 bytes. rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0] rsync: [sender] write error: Broken pipe (32) I've rolled back to version 3.0.5 (the most recent I had installed previously) and it seems to be doing the job. Tony M. -- С уважением, Дмитрий, начальник отдела UNIX-технологий, тел. 8 (495) 788-56-99, доб. 8255 -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- Best regards, Dmitry, signature.asc Description: OpenPGP digital signature -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Cannot build rsync 3.1.0 on MacOSX 10.8.5 with fileflags patch
However, attempting to build the new 3.1.0 release on a brand new Mountain Lion box with my standard 'fileflags' and 'crtimes' patches applied, make fails, reporting that 'force_change' is undeclared. Scott Lasley suggested a workaround for this: apply the 'hfs-compression' patch in addition to 'fileflags' and 'crimes' and everything works. patch -p1 patches/fileflags.diff patch -p1 patches/crtimes.diff patch -p1 patches/hfs-compression.diff ./prepare-source ./configure make sudo make install Evidently what was missing was a declaration for the force-change flag in main.c: the latter patch adds it. Looks like hfs-compression is a good patch to recommend for use on OS X installations in any case. Cheers, Tony M. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Rsync 3.1.0 failing [iobuf] on MacOSX 10.8.5 (was Re: Cannot build rsync 3.1.0 on MacOSX 10.8.5 with fileflags patch)
I got 3.1 to build all right on OS X but it won't run without stalling and lots of errors. Is it working for you or anyone else yet or have the problems come to light? Yes, now I'm using it in anger I'm seeing several fatal errors like the following (I'm syncing with a local mount point, no network access involved): need to write 129836 bytes, iobuf.out.buf is only 65532 bytes. rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0] rsync: [sender] write error: Broken pipe (32) need to write 401925 bytes, iobuf.out.buf is only 65532 bytes. rsync error: protocol incompatibility (code 2) at io.c(599) [sender=3.1.0] rsync: [sender] write error: Broken pipe (32) I've rolled back to version 3.0.5 (the most recent I had installed previously) and it seems to be doing the job. Tony M. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Cannot build rsync 3.1.0 on MacOSX 10.8.5 with fileflags patch
Returning to this list after a long hiatus: rsync 3 has been working very well
for me for many years, as a supplementary backup tool for MacOSX.
However, attempting to build the new 3.1.0 release on a brand new Mountain Lion
box with my standard 'fileflags' and 'crimes' patches applied, make fails,
reporting that 'force_change' is undeclared.
In fact, the problem occurs just with the 'fileflags' patch alone:
patch -p1 patches/fileflags.diff
./configure
make
This generates the error:
gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -I./popt -I./zlib -c main.c -o
main.o
main.c:846:6: error: use of undeclared identifier 'force_change'
if (force_change SYS_IMMUTABLE) {
^
1 error generated.
make: *** [main.o] Error 1
Building without the fileflags patch is successful.
Has anyone else noticed this behaviour?
Regards,
Tony Morton
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
