From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Crosstool-NG depends on awk/gawk
Date: Wed, 24 Nov 2010 17:11:43 +0100 [thread overview]
Message-ID: <20101124171143.7e1c497a@surf> (raw)
Hello,
I've finally tried the Crosstool-NG backend and it doesn't work because
it needs awk/gawk on the host, which isn't installed on my limited
Debian environment:
=======================================================================
Checking for 'grep'... /bin/grep
Checking whether '/bin/grep' supports -E... yes
Checking for 'sed'... /bin/sed
Checking whether '/bin/sed' supports -i and -e... yes
Checking for 'bash'... /bin/bash
Checking for 'cut'... /usr/bin/cut
Checking for 'install'... /usr/bin/install
Checking for 'make'... /usr/bin/make
Checking for 'gcc'... /usr/bin/gcc
Checking for 'awk'... no
Checking for 'gawk'... no
GNU awk was not found
Either you are missing entirely the needed tool,
or the version you have is too old.
=======================================================================
So probably we should build host-gawk before running Crosstool-NG
build, or make it a mandatory Buildroot dependency.
Other comment: Yann, it'd be really great if Crosstool-NG was hosted
behind a better connection than a DSL connection. Downloading at 50
KB/s is really frustrating :)
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next reply other threads:[~2010-11-24 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 16:11 Thomas Petazzoni [this message]
2010-11-24 18:29 ` [Buildroot] Crosstool-NG depends on awk/gawk Yann E. MORIN
2010-11-24 19:00 ` Michael S. Zick
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=20101124171143.7e1c497a@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