From: "Thiago A. Corrêa" <thiago.correa@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] native GCC not found in HEAD
Date: Tue, 25 Sep 2007 14:56:01 +0100 [thread overview]
Message-ID: <d6cda7730709250656u4b67c688q4f4e5fe83ce32571@mail.gmail.com> (raw)
Hi,
I've done an svn up today, and something has been broken since the
last time I tried a full build:
/bin/sh: /bin/-gcc: No such file or directory
copy_toolchain_lib_root: lib=libc.so.6 not found
make: *** [/root/novacomm/buildroot/buildroot-original/project_build_avr32/pppserver/root/lib/libc.so.6]
Error 255
gentoo-vm buildroot-original # which gcc
/usr/bin/gcc
gentoo-vm buildroot-original #
Been greping here and there, tried some hints from
http://www.oreilly.com.cn/samplechap/gnumake/ch12.pdf but can't find
where this is broken :(
Perhaps someone with more experience with buildroot could take a look into it?
Regards,
Thiago A Correa
next reply other threads:[~2007-09-25 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 13:56 Thiago A. Corrêa [this message]
2007-09-25 18:09 ` [Buildroot] native GCC not found in HEAD Ulf Samuelsson
2007-09-25 18:33 ` Thiago A. Corrêa
2007-09-25 19:06 ` Ulf Samuelsson
2007-09-25 22:05 ` Bernhard Fischer
2007-09-25 22:38 ` Ulf Samuelsson
2007-09-25 23:39 ` 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=d6cda7730709250656u4b67c688q4f4e5fe83ce32571@mail.gmail.com \
--to=thiago.correa@gmail.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