From: Daniel Jacobowitz <drow@mvista.com>
To: Rene Rebe <rene.rebe@gmx.net>
Cc: gcc@gcc.gnu.org
Subject: Re: building a gcc-3.3-prerelease cross-compiler
Date: Mon, 12 May 2003 14:22:00 -0000 [thread overview]
Message-ID: <20030512142238.GA13775@nevyn.them.org> (raw)
In-Reply-To: <20030512.135453.424242140.rene.rebe@gmx.net>
On Mon, May 12, 2003 at 01:54:53PM +0200, Rene Rebe wrote:
> Hi,
>
> I just started to test how far the gcc-3.3-prerelease progresses
> compiling our distribution build kit, but I get into trouble in the
> first step creating a cross compiler. (The configuration and scripts
> work flawlessly for gcc-2.95.3 and gxx-3.x).
>
> After the configure it claims to be configured as:
>
> Links are now set up to build a cross-compiler for i586-pc-linux-gnu
> from i686-nocross-linux-gnu.
>
> But running "make" it compiles the initial xgcc but bails out:
>
> checking whether the C compiler ( /home/rock-linux/rock-trunk/src.gccx.1052738245
> .1392.3356848690/gcc-3.3-20030508/objdir/gcc/xgcc -B/home/rock-linux/rock-trunk/s
> rc.gccx.1052738245.1392.3356848690/gcc-3.3-20030508/objdir/gcc/ -B/home/rock-linu
> x/rock-trunk/build/test-2.0.0-beta3-x86-pentium-mmx-generic-expert/tools.cross/us
> r/i586-pc-linux-gnu/bin/ -B/home/rock-linux/rock-trunk/build/test-2.0.0-beta3-x86
> -pentium-mmx-generic-expert/tools.cross/usr/i586-pc-linux-gnu/lib/ -isystem /home
> /rock-linux/rock-trunk/build/test-2.0.0-beta3-x86-pentium-mmx-generic-expert/tool
> s.cross/usr/i586-pc-linux-gnu/include -O2 -g ) works... no
> configure: error: installation or configuration problem: C compiler cannot create
> executables.
> make: *** [configure-target-libiberty] Error 1
>
> Where the error is:
>
> /home/rock-linux/rock-trunk/build/test-2.0.0-beta3-x86-pentium-mmx-generic-expert/tools.cross/usr/i586-pc-linux-gnu/bin/ld: cannot open crt1.o: No such file or directory
> collect2: ld returned 1 exit status
> configure: failed program was:
>
> #line 2407 "configure"
> #include "confdefs.h"
>
> main(){return(0);}
>
> But the crt1.o is installed by the glibc which would be built after we
> created the cross-compiler ...
>
> Any ideas?
You can't build target libraries until after you've built glibc.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-12 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 12:00 Rene Rebe
2003-05-12 14:22 ` Daniel Jacobowitz [this message]
2003-05-12 16:51 ` Rene Rebe
2003-05-12 16:59 ` Paul Koning
2003-05-12 19:24 ` Rene Rebe
2003-11-05 14:12 ` Rene Rebe
2003-05-13 15:46 ` Michael Eager
2003-05-13 16:07 ` Rene Rebe
2003-05-13 18:56 ` Michael Eager
2003-05-13 19:44 ` Rene Rebe
2003-05-13 20:34 ` Michael Eager
2003-05-13 22:14 ` Rene Rebe
2003-05-12 17:04 ` Joseph S. Myers
2003-05-12 17:13 ` Daniel Jacobowitz
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=20030512142238.GA13775@nevyn.them.org \
--to=drow@mvista.com \
--cc=gcc@gcc.gnu.org \
--cc=rene.rebe@gmx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).