usage of xfsctrl for embedded development / uuid question
A message that is not in the archive (sent off-list or not yet received): 17182907.184441263481368019.JavaMail.www@wsfrf1112
[Please wrap you emails at 72 columns]
Quoted 11 lines · On Thu, Jan 14, 2010 at 04:02:48PM +0100, [email protected] wrote:
Hi
I would like to use the xfsctl for trying directio and realtime feature on my gnu-linux embeded system (i have a "homemade" sdk).
It seems that the xfsctl function is defined inline, and that all i need is in
inlude/xfs/xfs.hinlude/xfs/xfs_fs.hinlude/xfs/platform_deps.hinlude/xfs/linux.h
Quoted 5 lines
So, for installing the dev files, it should be enought to do
tar -xvf xfsprogs-3.1.0.tar.gz
cd xfsprogs-3.1.0.tar.gz
./configure --build=${HOST} --host=${TARGET}
$MAKE -C include install-dev PKG_INC_DIR=${TOOLCHAIN_SYSROOT}/usr/include/xfs
install-dev is dependent on a full build of xfsprogs.
Why not just include the xfsprogs-dev package (or equivalent) from your base distro?
Quoted 8 lines
So here are my remarks :
(1) uuid configuration problems :
The package_uuiddev.m4 search for the function
uuid_compare. This unction is present in the uuid included in e2fsprogs, but not in the OSSP uuid (http://www.ossp.org/pkg/lib/uuid/). So the configuration is ok but the compilation fails.
I doubt anyone has tried to build xfsprogs against that uuid package before. Looks like it would need autoconf support to detect, then a bunch of code changes to support the different function prototype that the uuid_compare in the OSSP library has. I'm not sure what best way to do this would be.
Quoted 2 lines
The package_uuiddev.m4 search for uuid headers in multiple path but only one is included (in
linux.hfor example).
Sure - that's because we support multiple platforms and some level of abstraction is required to do that cleanly.
Quoted 7 lines
I think there is a bug with th definition of libuuid in package_uuiddev.m4 (not sure)
(2) uuid requirement
As uuid seems to be not required for my application, i suggest a patch that allow to ignore the absence of this dependance.
It doesn't work like that - just about every xfs utility that is build uses uuids in some form or another. IOWs, support needs to be present for the correct working of the utilities. Hence we cannot build xfsprogs without uuid support....
Quoted 11 lines
(3) regeneration of configure
The regeneration of configure fails whith this message
# rm configure # make configure [...] autoconf configure.in:101: error: possibly undefined macro: AC_HAVE_BLKID_TOPO If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation.
'make distclean' is the correct way to remove the configuration and rebuild it. That should make the problem go away.
Cheers,
Dave.
Signature · 7 lines
Dave Chinner [email protected] _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs
Quoted 15 lines · Dave Chinner
[Please wrap you emails at 72 columns]
Quoted 11 lines
(3) regeneration of configure
The regeneration of configure fails whith this message
# rm configure
# make configure
[...]
autoconf
configure.in:101: error: possibly undefined macro:AC_HAVE_BLKID_TOPO
If this token and others are legitimate, please usem4_pattern_allow. See the Autoconf documentation.
Quoted 2 lines
'make distclean' is the correct way to remove the configuration and rebuild it. That should make the problem go away.
This is also a bug thanks to yours truly in the latest release, Christoph sent a patch to fix it:
[PATCH] xfsprogs: add package_blkid.m4 to the distributed files
-Eric
Quoted 3 lines
Cheers,
Dave.
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs