From: Hebbar <gururajakr@sanyo.co.in>
To: buildroot@busybox.net
Subject: [Buildroot] make error with Kismet even if not selected
Date: Wed, 31 Oct 2007 01:21:54 -0700 (PDT) [thread overview]
Message-ID: <13504645.post@talk.nabble.com> (raw)
In-Reply-To: <47273782.1000900@linuxtv.org>
Hi,
i get an error as below when "make world" is given. This is with todays
buildroot snapshot i havent selected kismet in network utilities section.
still kismet tries to download and build.
Regards
Gururaja
checking build system type... i386-pc-linux-gnu
checking host system type... arm-unknown-linux-gnu
checking for arm-linux-gcc...
/home/guru/project/toolchain/uclibc/usr/bin/arm-linux-uclibcgnueabi-gcc -Os
-pipe -I/home/guru/project/toolchain/uclibc/usr/include
-I/home/guru/project/toolchain/uclibc/include
--sysroot=/home/guru/project/toolchain/uclibc/ -isysroot
/home/guru/project/toolchain/uclibc -mtune=arm9tdmi
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.
make: ***
[/home/guru/project/original/bldrt/buildroot/build_arm/kismet-2007-10-R1/.configured]
Error 77
--
View this message in context: http://www.nabble.com/svn-commit%3A-trunk-buildroot-package%3A--kismet-tf4717274.html#a13504645
Sent from the BuildRoot mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-10-31 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 9:16 [Buildroot] svn commit: trunk/buildroot/package: kismet thomasez at uclibc.org
2007-10-30 13:54 ` Michael Hunold
2007-10-31 8:21 ` Hebbar [this message]
2007-10-31 9:43 ` [Buildroot] make error with Kismet even if not selected Hamish Moffatt
2007-10-31 12:36 ` Thomas Lundquist
2007-10-31 13:18 ` Hamish Moffatt
2007-10-31 16:42 ` Sushi Sensei
2007-11-14 9:32 ` Thomas Lundquist
2007-10-31 20:46 ` Ulf Samuelsson
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=13504645.post@talk.nabble.com \
--to=gururajakr@sanyo.co.in \
--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