From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Help Building Buildroot
Date: Fri, 22 Jun 2007 20:20:54 +0200 [thread overview]
Message-ID: <20070622182054.GC2799@aon.at> (raw)
In-Reply-To: <1182533072.3733.7.camel@max.vermark.net>
On Fri, Jun 22, 2007 at 01:24:32PM -0400, A M wrote:
>Hi Guys,
>
>I can not seem to run make sucessfully using the daily snapshot of
>buildroot. It seems to always break just after downloading ccache. Here
>is the out put of what I have. I have tried this over and over again.
>
>I have also attached my .config file. Maybe there is something am
>missing.
>
>My target board is the WRAP 2E-E PC Engines
>(cd /home/amark/development/buildroot/build_i586/staging_dir/bin-ccache;
>\
> ln -fs i586-linux-uclibc-gcc i586-linux-gcc; \
> ln -fs i586-linux-uclibc-gcc i586-linux-cc; \
> ln -fs i586-linux-uclibc-gcc i586-linux-uclibc-cc);
>[ -f /home/amark/development/buildroot/build_i586/staging_dir/bin/i586-linux-uclibc-gcc ] && \
>
>mv /home/amark/development/buildroot/build_i586/staging_dir/bin/i586-linux-uclibc-gcc /home/amark/development/buildroot/build_i586/staging_dir/bin-ccache/
>make: ***
>[/home/amark/development/buildroot/build_i586/staging_dir/usr/bin/ccache] Error 1
The toolchain now resides in staging_dir/usr/bin (formerly it was in
staging_dir/bin), so this needs to be adjusted.
I will fix that up ASAP, disable ccache for now until this is fixed.
next prev parent reply other threads:[~2007-06-22 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 8:47 [Buildroot] svn commit: trunk/buildroot/target: device device/mips aldot at uclibc.org
2007-06-22 16:40 ` Julien Letessier
2007-06-22 17:24 ` [Buildroot] Help Building Buildroot A M
2007-06-22 18:20 ` Bernhard Fischer [this message]
2007-06-22 19:02 ` Bernhard Fischer
2007-06-22 19:15 ` A M
2007-06-22 20:55 ` A M
2007-06-22 21:07 ` Bernhard Fischer
2007-06-22 23:01 ` A M
2007-06-22 17:50 ` [Buildroot] svn commit: trunk/buildroot/target: device device/mips Bernhard Fischer
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=20070622182054.GC2799@aon.at \
--to=rep.dot.nop@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