From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] building toolchain fails
Date: Wed, 21 Oct 2009 14:38:06 +0200 [thread overview]
Message-ID: <87eiowrkgh.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <48B29D7D7EE043AF836DB1647ED0F5C6@apexjs> (Sagaert Johan's message of "Wed\, 21 Oct 2009 14\:26\:08 +0200")
>>>>> "Sagaert" == Sagaert Johan <sagaert.johan@skynet.be> writes:
Sagaert> Peter
Sagaert> See attachement concerning my debian
Sagaert> I will now look what i can do on the ubuntu machine.
Please keep discussion on the mailing list instead of mailing me
directly, so others can also follow.
Looking at your config.log makes the problem pretty obvious:
configure:1716: checking for C compiler default output
configure:1719: /home/johan/buildroot/output/build/staging_dir/usr/bin/arm-linux
-uclibc-gcc -Os -pipe -O2 -I/home/johan/buildroot/output/build/staging_dir/usr/
include -I/home/johan/buildroot/output/build/staging_dir/include --sysroot=/home
/johan/buildroot/output/build/staging_dir/ -isysroot /home/johan/buildroot/outpu
t/build/staging_dir -mabi=apcs-gnu -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_
FILE_OFFSET_BITS=64 conftest.c >&5
ccache: failed to create /ccache-2.4/cache (No such file or directory)
configure:1722: $? = 1
configure: failed program was:
#line 1700 "configure"
#include "confdefs.h"
int
main ()
{
;
return 0;
}
configure:1745: error: C compiler cannot create executables
So the problem is ccache somehow thinking it should write cache files to
/ccache-2.4.
Try disabling ccache and rebuild everything (rm -rf output; make).
--
Bye, Peter Korsgaard
next parent reply other threads:[~2009-10-21 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48B29D7D7EE043AF836DB1647ED0F5C6@apexjs>
2009-10-21 12:38 ` Peter Korsgaard [this message]
2009-10-21 13:42 ` [Buildroot] building toolchain fails works now with cache disabled Sagaert Johan
2009-10-21 15:37 ` Peter Korsgaard
2009-10-21 10:29 [Buildroot] building toolchain fails Sagaert Johan
2009-10-21 11:26 ` 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=87eiowrkgh.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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