From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] mkfs.xfs without xfs library - not possible to create xfsfs
Date: Tue, 13 Jul 2010 22:43:28 +0200 [thread overview]
Message-ID: <4C3CCFF0.3080407@gmx.net> (raw)
In-Reply-To: <4C3A1F60.7050009@gmx.net>
Am 11.07.2010 21:45, schrieb Ossy:
> Hi mailinglist,
>
> I tried to create an xfs filesystem. Unfortunatly there is a library
> missing. I looked around in the configuration menu, but all I found were
> the xfsprogs. Under libraries/filesystem there is no xfslib either.
>
> $ ./sbin/mkfs.xfs
> ./sbin/mkfs.xfs: can't load library 'libxfs.so.0'
>
The config.log of xfsprogs-3.0.3 includes a link to some e2fs library path:
...
configure:2544: checking for C compiler default output file name
configure:2566:
/home/ossy/buildroot/buildroot-dev/output/staging/usr/bin/arm-unknown-linux-uclibcgnueabi-gcc
--sysroot=/home/ossy/buildroot
/buildroot-dev/output/staging -Os -pipe -Os -mtune=arm926ej-s
-march=armv5te -mabi=aapcs-linux -msoft-float -D_LARGEFILE_SOURCE
-D_LARGEFIL
E64_SOURCE -D_FILE_OFFSET_BITS=64
-I/home/ossy/buildroot/buildroot-dev/output/staging/usr/include
-I/home/ossy/buildroot/buildroot-dev/outpu
t/staging/include
-I/home/ossy/buildroot/buildroot-dev/output/build/e2fsprogs-1.41.12/lib
-L/home/ossy/buildroot/buildroot-dev/output/build/
e2fsprogs-1.41.12/lib conftest.c >&5
...
I do not expect an e2fs-library path in xfsprogs.config. Maybe a
dependency to e2fs? Or is it just a bug?
I bumbed xfsprogs to 3.1.2 temporarily but this version failed to build.
Newer kernel versions and newer xfsprogs version fixes some issues for
using xfs on arm devices.
Regards,
Marcus
next prev parent reply other threads:[~2010-07-13 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 19:45 [Buildroot] mkfs.xfs without xfs library - not possible to create xfsfs Ossy
2010-07-13 20:43 ` Ossy [this message]
2010-07-15 19:20 ` Ossy
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=4C3CCFF0.3080407@gmx.net \
--to=ossy1980@gmx.net \
--cc=buildroot@busybox.net \
/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