From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: xfsprogs for-next build error on Debian Wheezy / amd64
Date: Wed, 10 Jun 2015 01:29:29 -0700 [thread overview]
Message-ID: <20150610082929.GA8496@infradead.org> (raw)
In-Reply-To: <20150610082415.GA23860@infradead.org>
On Wed, Jun 10, 2015 at 01:24:15AM -0700, Christoph Hellwig wrote:
> On Wed, Jun 10, 2015 at 06:19:14PM +1000, Dave Chinner wrote:
> > Does the problem go away after a 'make distclean'?
>
> No. Neither a distclean nor a fresh clone fixes the issue.
>
> Also disabling the crc32ctest target I get similar error in other
> code.
>
> Note that the master branch is doing fine.
I've biscted it to:
commit 2fe8a24dda8a2942a1168c745bf6743ae21991c0
Author: Dave Chinner <dchinner@redhat.com>
Date: Fri Jun 5 10:13:30 2015 +1000
libxfs: restructure to match kernel layout
but I still don't understand why it happens.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-06-10 8:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 7:06 xfsprogs for-next build error on Debian Wheezy / amd64 Christoph Hellwig
2015-06-10 8:19 ` Dave Chinner
2015-06-10 8:24 ` Christoph Hellwig
2015-06-10 8:29 ` Christoph Hellwig [this message]
2015-06-10 8:34 ` Dave Chinner
2015-06-10 8:40 ` Christoph Hellwig
2015-06-10 9:19 ` Dave Chinner
2015-06-11 16:03 ` Christoph Hellwig
2015-06-11 16:14 ` Eric Sandeen
2015-06-11 17:24 ` Christoph Hellwig
2015-06-17 10:31 ` Christoph Hellwig
2015-06-10 8:44 ` Dave Chinner
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=20150610082929.GA8496@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.