All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] 2011.11 zlib headers problem?
Date: Fri, 2 Dec 2011 15:58:01 +0100	[thread overview]
Message-ID: <20111202155801.57d914a5@skate> (raw)
In-Reply-To: <E06240F532254AA9BA06ECC0B98E6A19@beraninstruments.com.local>

Le Fri, 2 Dec 2011 13:50:28 -0000,
"Will Moore" <will.moore@beraninstruments.com> a ?crit :

> > Can you post the Buildroot .config you use to reproduce the problem?
> 
> See attached.

Interestingly, here, the build fails when building gdbhost:

configure: creating ./config.status
config.status: creating Makefile
./config.status: line 1123: gawk: command not found
config.status: creating testsuite/Makefile
./config.status: line 1123: gawk: command not found
config.status: creating config.h
./config.status: line 1149: gawk: command not found
config.status: error: could not create config.h
make[3]: *** [configure-libiberty] Error 1
make[2]: *** [all] Error 2
make[1]: *** [/home/test/outputs/will/toolchain/gdbhost-7.3.1/gdb/gdb]
Error 2

(Note: gawk is not available on my build machine, but has been built as
a dependency of ct-ng. I guess the gdbhost build process misses
$(HOST_DIR)/usr/bin in its PATH).

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-12-02 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 11:34 [Buildroot] 2011.11 zlib headers problem? Will Moore
2011-12-02 12:15 ` Will Moore
2011-12-02 12:17   ` Thomas Petazzoni
2011-12-02 13:50     ` Will Moore
2011-12-02 14:58       ` Thomas Petazzoni [this message]
2011-12-02 15:21         ` Will Moore
2011-12-02 14:59   ` Peter Korsgaard

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=20111202155801.57d914a5@skate \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.