From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] xfsprogs 3.0.3 without libxfs in rootfs
Date: Wed, 21 Jul 2010 08:58:22 +0200 [thread overview]
Message-ID: <20100721085822.5d2a34ae@surf> (raw)
In-Reply-To: <4C4613A2.90006@gmx.net>
Hello,
On Tue, 20 Jul 2010 23:22:42 +0200
Ossy <ossy1980@gmx.net> wrote:
> Since xfsprogs 3.0.3 doesn't build the required xfslib in the current
> tree. I tried to bump to the newer version.
> I figured out, that that br uses the old util-linux and not
> util-linux-ng. According to the debian package info, xfsprogs 3.1.2
> needs at least util-linux-ng 2.16.
Good. We really need to upgrade to util-linux-ng. It has been on my
TODO-list for a while, but I haven't managed to find the time for this.
> So I ran a green try with the
> util-linux-ng patch I've found in the mailinglist archives:
> http://article.gmane.org/gmane.comp.lib.uclibc.buildroot/16587/match=util+linux+ng
This patch doesn't use the AUTOTARGETS infrastructure to build
util-linux-ng, which is bad.
> Unfortunatly the build fails, because make claims about an unknown
> option "--sysroot":
> /usr/bin/make -j2 \
> -C
> /home/ossy/buildroot/buildroot-dev/output/build/util-linux-ng-2.16 \
> ARCH=arm \
>
> CC=/home/ossy/buildroot/buildroot-dev/output/staging/usr/bin/arm-unknown-linux-uclibcgnueabi-gcc
> --sysroot=/home/ossy/buildr
> oot/buildroot-dev/output/staging \
> OPT="-Os -pipe -Os -mtune=arm926ej-s -march=armv5te
> -mabi=aapcs-linux -msoft-float -D_LARGEFILE_SOURCE
> -D_LARGEFILE64_SOURC E -D_FILE_OFFSET_BITS=64
> -I/home/ossy/buildroot/buildroot-dev/output/staging/usr/include
> -I/home/ossy/buildroot/buildroot-dev/output/staging
> /include" \
> HAVE_SLANG="NO"
> /usr/bin/make: Unbekannte Option
> ?--sysroot=/home/ossy/buildroot/buildroot-dev/output/staging?
>
> It is the same make, used for all the other packages....
For a quick fix, replace:
CC=$(TARGET_CC)
by
CC="$(TARGET_CC)"
This should solve the "unknown --sysroot option" problem that you're
having.
But clearly the correct fix is to switch to AUTOTARGETS.
Cheers,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-07-21 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 21:22 [Buildroot] xfsprogs 3.0.3 without libxfs in rootfs Ossy
2010-07-21 6:58 ` Thomas Petazzoni [this message]
2010-07-24 17:02 ` Ossy
2010-07-30 8:43 ` Thomas Petazzoni
2010-07-30 19:48 ` Ossy
2010-07-31 13:03 ` Ossy
2010-07-31 14:33 ` 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=20100721085822.5d2a34ae@surf \
--to=thomas.petazzoni@free-electrons.com \
--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