From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: linux-xfs@oss.sgi.com
Subject: Re: xfsprogs: is it one issue?
Date: Sat, 08 Jun 2013 00:31:55 +0200 [thread overview]
Message-ID: <kotn0m$fmo$1@ger.gmane.org> (raw)
In-Reply-To: 20130526224805.GN24543@dastard
Dave Chinner wrote:
> On Mon, May 27, 2013 at 08:44:49AM +1000, Dave Chinner wrote:
>> On Sun, May 26, 2013 at 12:29:11AM +0800, Zhi Yong Wu wrote:
>> > HI,
>> >
>> > Did anyone hit this issue?
>> >
>> > [root@f15 xfsprogs]# make
>> > Building include
>> > Building libxfs
>> > [TEST] CRC32
>> > In file included from ../include/libxfs.h:584:0,
>> > from crc32.c:36:
>> > ../include/xfs/xfs_ialloc.h:75:2: error: unknown type name ?umode_t?
>> > gmake[2]: *** [crc32selftest] Error 1
>> > gmake[1]: *** [libxfs] Error 2
>> > make: *** [default] Error 2
>>
>> Install the latest kernel headers package for your distro.
>
> Actually, on debian it's part of a libc-dev package:
>
> $ grep -r umode /usr/include |head -1
> /usr/include/asm-generic/types.h:typedef unsigned short umode_t
> $ apt-file search /usr/include/asm-generic/types.h
> linux-libc-dev: /usr/include/asm-generic/types.h
> $
This won't work on recent kernels. Recent kernels export sanitized headers - it's called UAPI .
>From irc conversation:
00:07 < arekm> anyway current kernels export uapi headers (aka user space api headers,
https://lwn.net/Articles/507794/) and these don't export things like umode_t -
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/include/uapi/asm-generic/types.h
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/include/uapi/asm-generic/int-ll64.h
00:10 < bpm> arekm, linux/types.h has it on 3.10
00:10 < arekm> bpm: yes but this is not userspace installed header. it's kernel only
00:11 < arekm> bpm: linux-*/include/uapi/asm-generic/types.h is the one being installed for userspace
--
Arkadiusz Miśkiewicz, arekm / maven.pl
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-06-07 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 16:29 xfsprogs: is it one issue? Zhi Yong Wu
2013-05-25 19:43 ` Michael L. Semon
2013-05-25 22:57 ` Zhi Yong Wu
2013-05-25 23:11 ` Zhi Yong Wu
2013-05-26 23:11 ` Dave Chinner
2013-05-27 1:16 ` Zhi Yong Wu
2013-05-25 21:07 ` Eric Sandeen
2013-05-25 22:46 ` Zhi Yong Wu
2013-05-26 22:44 ` Dave Chinner
2013-05-26 22:48 ` Dave Chinner
2013-05-27 1:17 ` Zhi Yong Wu
2013-06-07 22:31 ` Arkadiusz Miśkiewicz [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='kotn0m$fmo$1@ger.gmane.org' \
--to=arekm@maven.pl \
--cc=linux-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