Lapo Luchini wrote:
> The real reason is the following test:
>
> configure:8272: checking whether to support extended attributes
> configure:8321: result: No extended attribute support found
>
> ...well, judging from configure lines 8272-8321 it seems rsync xattr
> support is only available in linux, darwin and freebsd.
>
> So, yes, that isn't "activating a switch" but rater "write a feature",
> which could be easy or difficult - I don't know enough about it right
> now to be the judge of that; definitely needs some more RTFM regarding
> xattrs on my side (and that needs time, which I have little on my hands,
> right now).
> As usual, the PTC principle applies there to have results faster.
> http://www.cygwin.com/acronyms/#PTC
It appears that cygwin has the xattr functions implemented and exported:
> $ grep setxattr /gnu/winsup/src/winsup/cygwin/cygwin.din
> fsetxattr SIGFE
> lsetxattr SIGFE
> setxattr SIGFE
So it could be as simple as using the existing linux support on cygwin too,
by doing something like:
$ diff -pu configure.in.orig configure.in
--- configure.in.orig 2009-09-16 13:10:53.125000000 +0100
+++ configure.in 2009-09-16 13:11:41.437500000 +0100
@@ -933,7 +933,7 @@ if test x"$enable_xattr_support" = x"no"
AC_MSG_RESULT(no)
else
case "$host_os" in
- *linux*)
+ *linux* | *cygwin*)
AC_MSG_RESULT(Using Linux xattrs)
AC_DEFINE(HAVE_LINUX_XATTRS, 1, [True if you have Linux xattrs])
AC_DEFINE(SUPPORT_XATTRS, 1)
ad...@ubik /usr/src/rsync/rsync-3.0.5
... followed of course by regenerating configure.sh.
I haven't tested this (my cpu usage is already 100% and likely to stay that
way for the next day or two!), but maybe you'd like to give it a whirl?
cheers,
DaveK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
