From: Paul Chavent <paul.chavent@fnac.net>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: usage of xfsctrl for embedded development / uuid question
Date: Fri, 15 Jan 2010 22:11:21 +0100 [thread overview]
Message-ID: <4B50D9F9.1010809@fnac.net> (raw)
In-Reply-To: <20100115124617.GJ28498@discord.disaster>
> It's a wrapper around ioctl(). You can call ioctl() directly
> on not need xfsctl at all...
Right, but i found nowhere the structures and the definition of XFS_IOC_* in the headers "exported" by the kernel.
So i have two solutions :
(1) i add -I/path_to_the_kernel_sources/fs to the cflags of my project.
(2) i install those headers in my sysroot.
I thought that those solutions where worst that only install headers from the xfsprogs package.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-01-15 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5340782.170001263558076439.JavaMail.www@wsfrf1111>
2010-01-15 12:46 ` usage of xfsctrl for embedded development / uuid question Dave Chinner
2010-01-15 21:11 ` Paul Chavent [this message]
2010-01-17 11:46 ` Christoph Hellwig
[not found] <17182907.184441263481368019.JavaMail.www@wsfrf1112>
2010-01-15 0:29 ` Dave Chinner
2010-01-15 1:32 ` Eric Sandeen
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=4B50D9F9.1010809@fnac.net \
--to=paul.chavent@fnac.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox