From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] nbd fails to compile with /usr/bin/klcc: unknown option: --sysroot=
Date: Thu, 24 Jun 2010 09:44:17 +0200 [thread overview]
Message-ID: <20100624094417.37048649@surf> (raw)
In-Reply-To: <201006240053.12651.PeterHuewe@gmx.de>
On Thu, 24 Jun 2010 00:53:12 +0200
Peter H?we <PeterHuewe@gmx.de> wrote:
> the atngw100_defconfig has nbd client and server enabled, and unfortunately it fails to compile, with the message
>
> /usr/bin/klcc: unknown option: --sysroot=/avr/buildroot/output/staging/
>
> $klcc --version
> x86_64-pc-linux-gnu-gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.3)
>
> How can I fix this ? - Unfortunately I'm not that into the whole buildroot system (yet, but I'd like to learn and contribute to it).
It's because you have klcc installed on your development system, nbd
detects it and uses it. Unfortunately, it doesn't understand all the
usual gcc options.
You have two options to solve this problem:
*) Pass the --disable-klcc option to NBD's configure script. You could
add this to NBD_CONF_OPT.
*) Update to nbd 2.9.15 (the current version in Buildroot is 2.9.11),
which has removed support for klcc.
In any case, don't forget to send a patch ! :-)
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-06-24 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 22:53 [Buildroot] nbd fails to compile with /usr/bin/klcc: unknown option: --sysroot= Peter Hüwe
2010-06-24 7:44 ` Thomas Petazzoni [this message]
2010-06-24 10:46 ` [Buildroot] [PATCH] nbd: Bump nbd to version 2.9.15 and remove klcc issue Peter Huewe
2010-06-24 15:35 ` Peter Korsgaard
2010-06-24 10:47 ` [Buildroot] nbd fails to compile with /usr/bin/klcc: unknown option: --sysroot= Peter Hüwe
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=20100624094417.37048649@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