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: compilation of gcc-cross-intermediate-4.4.2 failed due to lack of fenv.h
Date: Mon, 4 Jan 2010 10:10:57 -0800	[thread overview]
Message-ID: <20100104181057.GA4326@gmail.com> (raw)
In-Reply-To: <op.u5sogndnmn1qzu@guohr-laptop-ubuntu>

On (31/12/09 16:56), Guo Hongruan wrote:
> I am afraid that the failure is not so easy.
> 
> Today, I recompile the following builds:
> MACHINE=qemux86 DISTRO=micro-uclibc
> MACHINE=qemuarm DISTRO=micro-uclibc
> MACHINE=qemumips DISTRO=micro-uclibc
> 
> only qemuarm works. But the problem is that the uclibc configuration
> in qemuarm building has not defined UCLIBC_HAS_FENV, and the
> configuration options of gcc-cross-intermedia lacks
> --disable-decimal-float. So according the previous analysis, the
> qemuarm building should failed and reported the same reason.
> 
> Why did qemuarm build pass? I can not figure it out.

decimal float is enabled by default for powerpc, x86 and x86_64 in gcc
thats why you see that it works ok on arm because its disabled by
default for arm. So yes for uclibc on these architectures you need to
disable it because uclibc does not have decimal floating library
implementation. Thats why in my patch in previous email I disabled 
it for all uclibc based builds of gcc. 
It should be disabled for mips as the code in gcc seems
like.  If you could post your gcc build logs somewhere I can have a
look.

-Khem




      reply	other threads:[~2010-01-04 18:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28  3:49 compilation of gcc-cross-intermediate-4.4.2 failed due to lack of fenv.h Guo Hongruan
2009-12-28 18:53 ` Khem Raj
2009-12-31  8:56   ` Guo Hongruan
2010-01-04 18:10     ` Khem Raj [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=20100104181057.GA4326@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.