From: "Luo Yong" <yong.personal.mail@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: error occured when cross compiling gcc
Date: Wed, 28 Jun 2006 05:46:00 -0000 [thread overview]
Message-ID: <e1d802b70606272246y39e6098em601df86b0a5aa440@mail.gmail.com> (raw)
In-Reply-To: <e1d802b70606272123s6b435be6q5dbb1da0eb1c29df@mail.gmail.com>
The content of config.log is
===
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:600: checking host system type
configure:621: checking target system type
configure:639: checking build system type
configure:694: checking for a BSD compatible install
configure:747: checking whether ln works
configure:771: checking whether ln -s works
configure:1825: checking for gcc
configure:1938: checking whether the C compiler (gcc ) works
configure:1954: gcc -o conftest conftest.c 1>&5
configure:1980: checking whether the C compiler (gcc ) is a cross-compiler
configure:1985: checking whether we are using GNU C
configure:2013: checking whether gcc accepts -g
configure:2080: checking for gnatbind
configure:2145: checking whether compiler driver understands Ada
configure:2177: checking how to compare bootstrapped objects
configure:2275: checking for correct version of gmp.h
configure:2288: gcc -c -g -O2 conftest.c 1>&5
configure:2278:17: error: gmp.h: No such file or directory
configure: In function 'main':
configure:2282: error: 'choke' undeclared (first use in this function)
configure:2282: error: (Each undeclared identifier is reported only once
configure:2282: error: for each function it appears in.)
configure:2282: error: expected ';' before 'me'
configure: failed program was:
#line 2277 "configure"
#include "confdefs.h"
#include "gmp.h"
int main() {
#if __GNU_MP_VERSION < 3
choke me
#endif
; return 0; }
configure:3313: checking for bison
configure:3313: checking for byacc
configure:3313: checking for yacc
configure:3353: checking for bison
configure:3392: checking for gm4
configure:3431: checking for flex
configure:3471: checking for flex
configure:3510: checking for makeinfo
configure:3563: checking for expect
configure:3604: checking for runtest
configure:3652: checking for i686-pc-linux-gnu-ar
configure:3727: checking for i686-pc-linux-gnu-as
configure:3802: checking for i686-pc-linux-gnu-dlltool
configure:3833: checking for dlltool
configure:3877: checking for i686-pc-linux-gnu-ld
configure:3952: checking for i686-pc-linux-gnu-lipo
configure:3983: checking for lipo
configure:4027: checking for i686-pc-linux-gnu-nm
configure:4102: checking for i686-pc-linux-gnu-ranlib
configure:4172: checking for i686-pc-linux-gnu-strip
configure:4242: checking for i686-pc-linux-gnu-windres
configure:4273: checking for windres
configure:4317: checking for i686-pc-linux-gnu-objcopy
configure:4392: checking for i686-pc-linux-gnu-objdump
configure:4474: checking for arm-elf-linux-ar
configure:4549: checking for arm-elf-linux-as
configure:4624: checking for arm-elf-linux-cc
configure:4624: checking for arm-elf-linux-gcc
configure:4699: checking for arm-elf-linux-c++
configure:4699: checking for arm-elf-linux-g++
configure:4699: checking for arm-elf-linux-cxx
configure:4699: checking for arm-elf-linux-gxx
configure:4774: checking for arm-elf-linux-dlltool
configure:4849: checking for arm-elf-linux-gcc
configure:4919: checking for arm-elf-linux-gcj
configure:4994: checking for arm-elf-linux-gfortran
configure:5069: checking for arm-elf-linux-ld
configure:5144: checking for arm-elf-linux-lipo
configure:5219: checking for arm-elf-linux-nm
configure:5294: checking for arm-elf-linux-objdump
configure:5369: checking for arm-elf-linux-ranlib
configure:5439: checking for arm-elf-linux-strip
configure:5514: checking for arm-elf-linux-windres
configure:5588: checking where to find the target ar
configure:5613: checking where to find the target as
configure:5638: checking where to find the target cc
configure:5663: checking where to find the target c++
configure:5691: checking where to find the target c++ for libstdc++
configure:5719: checking where to find the target dlltool
configure:5744: checking where to find the target gcc
configure:5769: checking where to find the target gcj
configure:5797: checking where to find the target gfortran
configure:5825: checking where to find the target ld
configure:5850: checking where to find the target lipo
configure:5865: checking where to find the target nm
configure:5890: checking where to find the target objdump
configure:5915: checking where to find the target ranlib
configure:5940: checking where to find the target strip
configure:5965: checking where to find the target windres
configure:6018: checking whether to enable maintainer-specific
portions of Makefiles
configure:6065: checking if symbolic links between directories work
===
Thanks.
On 6/28/06, Tim Prince <timothyprince@sbcglobal.net> wrote:
> Luo Yong wrote:
>
> > checking for C compiler default output file name... configure: error:
> > C compiler cannot create executables
> > See `config.log' for more details.
>
> >
> > How can I solve this problem?
>
> In part, by following that advice?
>
next prev parent reply other threads:[~2006-06-28 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 4:23 Luo Yong
2006-06-28 5:15 ` Tim Prince
2006-06-28 5:46 ` Luo Yong [this message]
2006-06-28 11:39 ` Tim Prince
2006-06-28 11:49 ` Rupert Wood
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=e1d802b70606272246y39e6098em601df86b0a5aa440@mail.gmail.com \
--to=yong.personal.mail@gmail.com \
--cc=gcc-help@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).