From: Hamish Guthrie <hamish.guthrie@sonycom.com>
To: buildroot@busybox.net
Subject: [Buildroot] arch support
Date: Tue, 13 Jan 2009 10:04:06 +0100 [thread overview]
Message-ID: <496C5906.6080309@sonycom.com> (raw)
In-Reply-To: <87iqokh9mt.fsf@macbook.be.48ers.dk>
Hi,
>
> Strange - Are you building in a clean tree? What host are you using?
>
Yes, building against a clean tree. I have tried this on 4 different
build hosts:
1) Centos 5.0 i386: gcc4.1.2 - FAIL
2) Debian Etch i386: gcc4.1.2 - FAIL
3) Ubuntu 7.04 i386: gcc4.1.2 - FAIL
4) Ubuntu 8.10 i386: gcc4.3.2 - PASS
For all of the failures, the appropriate part of the config.log file is
as follows:
configure:2567: checking for suffix of object files
configure:2588:
/tmp/br/powerpc/toolchain_build_powerpc/gcc-4.3.2-initial/./gcc/xgcc
-B/tmp/br/powerpc/toolchain_build_powerpc/gcc-4.3.2-initial/./gcc/
-B/tmp/br/powerpc/build_powerpc/staging_dir/usr/powerpc-linux-uclibc/bin/
-B/tmp/br/powerpc/build_powerpc/staging_dir/usr/powerpc-linux-uclibc/lib/
-isystem
/tmp/br/powerpc/build_powerpc/staging_dir/usr/powerpc-linux-uclibc/include
-isystem
/tmp/br/powerpc/build_powerpc/staging_dir/usr/powerpc-linux-uclibc/sys-include
-c -g -Os conftest.c >&5
/tmp/br/powerpc/toolchain_build_powerpc/gcc-4.3.2-initial/./gcc/cc1:
error while loading shared libraries: libmpfr.so.1: cannot open shared
object file: No such file or directory
configure:2591: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME "GNU C Runtime Library"
| #define PACKAGE_TARNAME "libgcc"
| #define PACKAGE_VERSION "1.0"
| #define PACKAGE_STRING "GNU C Runtime Library 1.0"
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2605: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
Unfortunately, the Ubuntu 8.10 machine I used last night to test on is
not available to me at the moment, however, I am currently getting a new
VM set up with Ubuntu 8.10 on it, on which I will install gcc4.1.2 to
see if that is in fact the culprit, but I am not really convinced.
Any thoughts would be appreciated
--
Hamish
next prev parent reply other threads:[~2009-01-13 9:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 8:54 [Buildroot] arch support Peter Korsgaard
2009-01-12 9:00 ` Hans-Christian Egtvedt
2009-01-12 9:08 ` Peter Korsgaard
2009-01-12 10:33 ` Ulf Samuelsson
2009-01-12 10:35 ` Ulf Samuelsson
2009-01-12 9:07 ` Bernhard Reutner-Fischer
2009-01-12 9:22 ` Peter Korsgaard
2009-01-12 10:59 ` Hinko Kocevar
2009-01-12 11:05 ` Peter Korsgaard
2009-01-12 12:48 ` Hinko Kocevar
2009-01-12 20:17 ` Peter Korsgaard
2009-01-12 14:31 ` Hamish Guthrie
2009-01-12 14:38 ` Peter Korsgaard
2009-01-13 9:04 ` Hamish Guthrie [this message]
2009-01-13 11:40 ` Hinko Kocevar
2009-01-15 22:01 ` 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=496C5906.6080309@sonycom.com \
--to=hamish.guthrie@sonycom.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