public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Pieter Thysebaert <pthyseba@intec.rug.ac.be>
To: erwan ancel <erwan.ancel@free.fr>
Cc: gcc-help@gcc.gnu.org
Subject: Re: building a cross compiler
Date: Thu, 01 May 2003 20:42:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0305012053330.23413-100000@plinius.intec2.rug.ac.be> (raw)
In-Reply-To: <1051729148.3290.6.camel@brisedorient>



On 30 Apr 2003, erwan ancel wrote:

> Hi,
>
> I am trying to build the gcc 3.2.3 under linux for Windows Cygwin
> target.
> my configure parameters are:
> ./configure -v --prefix=/usr/cross-compile --target=i386-mingw32
> --with-gnu-as --with-gnu-ld --disable-multilib
>
> when typing make, the xgcc is built, but I got the error:
> checking whether the C compiler (/home/awa/toto/gcc-3.2.3/gcc/xgcc
> -B/home/awa/toto/gcc-3.2.3/gcc/ -B/usr/cross-compile/i386-mingw32/bin/
> -B/usr/cross-compile/i386-mingw32/lib/ -isystem
> /usr/cross-compile/i386-mingw32/include -O2 -g -O2 ) works... no
> configure: error: installation or configuration problem: C compiler
> cannot create executables.
> make: *** [configure-target-libiberty] Erreur 1

check the last lines of config.log, it will include the error as reported
by the compiler when attempting to compile a test program.


Have you built cross-binutils AND put them (or rather, the name
of the directory
containing them) in your PATH variable?

BTW you're configuring for mingw, not cygwin .

Pieter

  parent reply	other threads:[~2003-05-01 20:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 18:59 erwan ancel
2003-04-30 20:40 ` LLeweLLyn Reese
2003-04-30 21:10   ` erwan ancel
2003-05-01  4:16   ` npat
2003-05-01 20:42 ` Pieter Thysebaert [this message]
2003-05-01 20:36   ` erwan ancel
  -- strict thread matches above, loose matches on Subject: below --
2001-01-12  3:22 David Korn
2001-01-12 10:05 ` Albert Niessner
2001-01-11 17:04 Albert Niessner
1999-12-11 12:26 Building " Mark A. Framness
1999-12-11 13:51 ` Mumit Khan
1999-12-31 22:24   ` Mumit Khan
1999-12-31 22:24 ` Mark A. Framness

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=Pine.LNX.4.44.0305012053330.23413-100000@plinius.intec2.rug.ac.be \
    --to=pthyseba@intec.rug.ac.be \
    --cc=erwan.ancel@free.fr \
    --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).