On Mar 29 03:02, Yaakov (Cygwin/X) wrote:
> On Tue, 2011-03-29 at 09:53 +0200, Corinna Vinschen wrote:
> > On Mar 29 02:43, Yaakov (Cygwin/X) wrote:
> > > I see two ways to resolve this:
> > >
> > > 1) Move include/attr/xattr.h to include/sys/xattr.h, and ship libattr's
> > > attr/xattr.h in libat
On Tue, 2011-03-29 at 09:53 +0200, Corinna Vinschen wrote:
> On Mar 29 02:43, Yaakov (Cygwin/X) wrote:
> > I see two ways to resolve this:
> >
> > 1) Move include/attr/xattr.h to include/sys/xattr.h, and ship libattr's
> > attr/xattr.h in libattr-devel, exactly as is done on Linux:
> >
> > 2) Ins
On Mar 29 09:53, Corinna Vinschen wrote:
> On Mar 29 02:43, Yaakov (Cygwin/X) wrote:
> > Historically, the *xattr functions were first provided by SGI libattr
> > and prototyped in . Later, glibc added them under
> > [1], and (on Linux) libattr still provides the symbols for
> > ABI compatibility
On Mar 29 02:43, Yaakov (Cygwin/X) wrote:
> Historically, the *xattr functions were first provided by SGI libattr
> and prototyped in . Later, glibc added them under
> [1], and (on Linux) libattr still provides the symbols for
> ABI compatibility but they are now just wrappers.
>
> (FWIW, Darwin
Historically, the *xattr functions were first provided by SGI libattr
and prototyped in . Later, glibc added them under
[1], and (on Linux) libattr still provides the symbols for
ABI compatibility but they are now just wrappers.
(FWIW, Darwin also provides these symbols in [2].)
This can be seen
