Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Kletschke <kletschke@synertronixx.de>
To: buildroot@busybox.net
Subject: [Buildroot] gcc-4.1.2 eabi softfloat toolchain, undefined reference to "raise"
Date: Fri, 4 May 2007 09:34:25 +0200	[thread overview]
Message-ID: <20070504073424.GA1982@z1.synertronixx> (raw)
In-Reply-To: <20070503095759.GA552@aon.at>

Am 2007-05-03 11:57 +0200 schrieb Bernhard Fischer:

> A quick google for these keywords:
> __div0 raise arm softfloat

Well, one trace leads to an uClibc-gcc-41-raise-error.patch which yields
into a 404. But as I understand this "fixes" uClibc to compile but does
not change the toolchain itself.

Another trace yields into a discussion suggesting replacing u-boot's
__div(0) by a raise() stub. May be I did something like that with my
very ugly hack.

So did I understand right, that the libgcc calls raise() which is
provided by glibc not uClibc?

How comes only u-boot triggers that? I compiled many other stuff with
this toolchain, kernel and userspace leading into perfect working
binaries.

Kind regards, Konsti

-- 
synertronixx GmbH
Dipl.-Ing. (FH) Konstantin Kletschke
Vahrenwalder Str. 7
30165 Hannover
Tel.    : 0511 / 3574 - 661
Fax     : 0511 / 93 57 - 679
E-mail  : kletschke at synertronixx.de
Internet: http://www.synertronixx.de
Vertretungsberechtigte Gesch?ftsf?hrer:
Marc-Oliver Borck, Dr. Matthias Blaschke
Registergericht: Amtsgericht Hannover
Registernummer: HRB 59670
USt-ID: DE 216 559 901

      reply	other threads:[~2007-05-04  7:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26  8:02 [Buildroot] gcc-4.1.2 eabi softfloat toolchain, undefined reference to "raise" Konstantin Kletschke
2007-04-30 12:57 ` Bernhard Fischer
2007-05-03  8:35   ` Konstantin Kletschke
2007-05-03  9:57     ` Bernhard Fischer
2007-05-04  7:34       ` Konstantin Kletschke [this message]

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=20070504073424.GA1982@z1.synertronixx \
    --to=kletschke@synertronixx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox