From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Subject: xfsprogs for-next build error on Debian Wheezy / amd64
Date: Wed, 10 Jun 2015 00:06:04 -0700 [thread overview]
Message-ID: <20150610070604.GA9855@infradead.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 853 bytes --]
hch@brick:~/work/xfsprogs$ make
Building include
Building libxfs
[TEST] CRC32
In file included from crc32.c:61:0:
crc32table.h:4:1: error: ‘__le32’ undeclared here (not in a
function)
crc32table.h:4:1: error: expected expression before ‘__u32’
crc32table.h:4:20: error: expected expression before ‘__u32’
crc32table.h:4:39: error: expected expression before ‘__u32’
crc32table.h:4:58: error: expected expression before ‘__u32’
crc32table.h:5:1: error: expected expression before ‘__u32’
crc32table.h:5:20: error: expected expression before ‘__u32’
crc32table.h:5:39: error: expected expression before ‘__u32’
crc32table.h:5:58: error: expected expression before ‘__u32’
... and so on
Seems like we're not getting the right headers included in this
generated file, but I'm lost on what exactly is the error.
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-06-10 7:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 7:06 Christoph Hellwig [this message]
2015-06-10 8:19 ` xfsprogs for-next build error on Debian Wheezy / amd64 Dave Chinner
2015-06-10 8:24 ` Christoph Hellwig
2015-06-10 8:29 ` Christoph Hellwig
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=20150610070604.GA9855@infradead.org \
--to=hch@infradead.org \
--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.