All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: failure on gcc-cross-initial-4.2.4-r5 for i686
Date: Sat, 7 Mar 2009 17:35:28 -0800	[thread overview]
Message-ID: <200903071735.37618.raj.khem@gmail.com> (raw)
In-Reply-To: <1236463653.25861.321.camel@cheeto.emacinc.com>

On Saturday 07 March 2009 14:07:33 Travis Stratman wrote:
> Hello,
>
> I am trying to build an image for an i686 based machine (pentiumpro). I
> have it configured to use gcc 4.2.4, glibc 2.6.1, binutils 2.18.50.0.7.
>
> The build fails on do_compile in gcc-cross-initial. The log shows
> "checking for C compiler default output file name... configure: error: C
> compiler cannot create executables" in configure-stage2-intl.
>
> Looking at the config.log in gcc-4.2.4/build.i686-linux.i686-linux/intl
> shows:
> ----
> configure:2118: checking for C compiler default output file name
> configure:2121: 
> /opt/oe/EMAC-OE-x86/tmp/work/i686-linux/gcc-cross-initial-4.2.4-r5/gcc-4.2.
>4/build.i686-linux.i686-linux/./prev-gcc/xgcc
> -B/opt/oe/EMAC-OE-x86/tmp/work/i686-linux/gcc-cross-initial-4.2.4-r5/gcc-4.
>2.4/build.i686-linux.i686-linux/./prev-gcc/
> -B/opt/oe/EMAC-OE-x86/tmp/cross/i686/i686-linux/bin/ -O2 -g
> -fomit-frame-pointer   conftest.c  >&5
> /opt/oe/EMAC-OE-x86/tmp/cross/i686/i686-linux/bin/ld: crt1.o: No such file:
> No such file or directory
> collect2: ld returned 1 exit status
> ----
>
> If I recall correctly the crt1.o file is a start file provided by glibc,
> but I need to get gcc compiled first...

yes. gcc-initial is really very minimal gcc. It does not depend on anything 
except binutils. We make sure that it does not build stuff thats not needed at 
this stage.

>
> Any ideas on where to start? Is there any information that I can provide
> that would be helpful?

Are you using latest git? I do not get the error like yours for me it builds 
fine for i686-generic machine. Could you post your local.conf ?
are you using some pre existing distro and machine or defining your own.

Thx

-Khem





  reply	other threads:[~2009-03-08  1:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-07 22:07 failure on gcc-cross-initial-4.2.4-r5 for i686 Travis Stratman
2009-03-08  1:35 ` Khem Raj [this message]
2009-03-09 22:18   ` Travis Stratman
2009-03-09 22:35     ` Khem Raj
2009-03-10 15:40       ` Travis Stratman
2009-03-10 17:35         ` Khem Raj
2009-03-11  3:05           ` Denys Dmytriyenko
2009-03-11  3:41             ` Khem Raj
2009-03-11 21:28             ` Leon Woestenberg
2009-03-12  2:22               ` Denys Dmytriyenko
2009-03-13 21:22             ` Stanislav Brabec
2009-03-11 15:36           ` Travis Stratman
2009-03-11 22:44           ` Travis Stratman

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=200903071735.37618.raj.khem@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.