| To: | Paul Chavent <paul.chavent@xxxxxxxx> |
|---|---|
| Subject: | Re: usage of xfsctrl for embedded development / uuid question |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Sun, 17 Jan 2010 06:46:58 -0500 |
| Cc: | Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <4B50D9F9.1010809@xxxxxxxx> |
| References: | <5340782.170001263558076439.JavaMail.www@wsfrf1111> <20100115124617.GJ28498@xxxxxxxxxxxxxxxx> <4B50D9F9.1010809@xxxxxxxx> |
| User-agent: | Mutt/1.5.19 (2009-01-05) |
On Fri, Jan 15, 2010 at 10:11:21PM +0100, Paul Chavent wrote: >> 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. You can just install the xfsprogs headers only by doing it yourself or filtering the installed files in your package manager. I'm not sure it's really worth it to support this special environment in the xfsprogs build system. > > _______________________________________________ > xfs mailing list > xfs@xxxxxxxxxxx > http://oss.sgi.com/mailman/listinfo/xfs ---end quoted text--- |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] xfstests 131: kill locktest process in cleanup & better error msgs, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [PATCH 6/9] xfsprogs: fix trivial warnings in xfs_fsr, Christoph Hellwig |
| Previous by Thread: | Re: usage of xfsctrl for embedded development / uuid question, Paul Chavent |
| Next by Thread: | [PATCH] mkfs: fix mkfs when blkid fails, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |