All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32  build broken.
Date: Fri, 28 Sep 2007 00:12:16 +0200	[thread overview]
Message-ID: <20070927221216.GF20951@aon.at> (raw)
In-Reply-To: <1190854406.4933.78.camel@elrond.atmel.sweden>

On Thu, Sep 27, 2007 at 02:53:26AM +0200, Ulf Samuelsson wrote:
>The atngw100small also fails with the following error:
>
>configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
>make[2]: *** [configure-target-libiberty] Fel 1
>make[2]: *** Inv?ntar oavslutade jobb...
>make[1]: *** [all] Fel 2
>
>This is the same error you get when you try to build the ARM with
>softfloat.

I cannot reproduce this. I've double-checked that the sample arm926t
(integrator CP, IIRC) builds and works fine with and without softfloat
(after deleting that wrong uClibc-0.9.29-soft-fp.patch, of course).

Can you reproduce this error with the provided defconfig in
target/device/ARM/integrator_whatever ?

>Since the AVR32 does not have an FPU, this is always softfloat.
>
>There is something screwed up with the linking process
>when using the current trunk.

We'll track it down.
>
>Not all libraries are found, so gcc configure
>cannot link and this sets some flags resulting in the error above.
>
>The ARM softfloat patch was trying to overcome the fact
>that libgcc.a is not used/found by the uClibc build.

This is not really an accurate approach i'd say (but i didn't look
closely), but i take it that you're aware of this.

Thanks,

  parent reply	other threads:[~2007-09-27 22:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27  0:53 [Buildroot] AVR32 build broken Ulf Samuelsson
2007-09-27  1:11 ` [Buildroot] Endianness problem Leonid
2007-09-27 22:12 ` Bernhard Fischer [this message]
2007-09-27 23:29   ` [Buildroot] AVR32 build broken Ulf Samuelsson
2007-09-28  6:53   ` Ulf Samuelsson
2007-09-28  7:37     ` 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=20070927221216.GF20951@aon.at \
    --to=rep.dot.nop@gmail.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 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.