From: Andreas Gruenbacher <agruen@suse.de>
To: Petr Salinger <Petr.Salinger@seznam.cz>, acl-devel@nongnu.org
Cc: Christoph Hellwig <hch@infradead.org>,
531950-quiet@bugs.debian.org, Nathan Scott <nscott@aconex.com>,
Aurelien Jarno <aurelien@aurel32.net>,
xfs@oss.sgi.com
Subject: Re: Bug#531950: attr: FTBFS on GNU/kFreeBSD
Date: Fri, 19 Jun 2009 17:37:57 +0200 [thread overview]
Message-ID: <200906191737.58393.agruen@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0906151211550.15794@sci.felk.cvut.cz>
On Monday 15 June 2009 12:26:12 Petr Salinger wrote:
> We would really appreciate to have either "#ifdef ENODATA" or
> "#ifdef __linux__" applied to current debian version of package.
> The debian maintainer does not want to diverge from (future) upstream,
> which is quite understandable.
>
> Would be possible to special case ENODATA as 1st step and postpone
> adding of syscall support later ?
Yes, done.
> The current situation (unbuildable attr under Bebian) prevents
> building of many other packages, namely kdelibs (and whole KDE 3.x),
> kde4libs (and whole KDE 4.x) and gnome-vfs (almost whole GNOME) and even
> vim editor under Debian GNU/kFreeBSD.
Thanks,
Andreas
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-06-19 15:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1450746396.6081061244543230576.JavaMail.root@mail-au.aconex.com>
2009-06-09 10:31 ` Bug#531950: attr: FTBFS on GNU/kFreeBSD Nathan Scott
2009-06-09 11:35 ` Petr Salinger
2009-06-09 12:10 ` Christoph Hellwig
2009-06-14 16:35 ` Aurelien Jarno
2009-06-14 20:33 ` Christoph Hellwig
2009-06-14 20:56 ` Aurelien Jarno
2009-06-15 9:42 ` Christoph Hellwig
2009-06-15 10:26 ` Petr Salinger
2009-06-15 10:05 ` Aurelien Jarno
2009-06-19 15:37 ` Andreas Gruenbacher [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200906191737.58393.agruen@suse.de \
--to=agruen@suse.de \
--cc=531950-quiet@bugs.debian.org \
--cc=Petr.Salinger@seznam.cz \
--cc=acl-devel@nongnu.org \
--cc=aurelien@aurel32.net \
--cc=hch@infradead.org \
--cc=nscott@aconex.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox