Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-11-05
Date: Sun, 6 Nov 2016 20:33:46 +0100	[thread overview]
Message-ID: <20161106193346.GA27313@waldemar-brodkorb.de> (raw)
In-Reply-To: <20161106150623.2b7fd549@free-electrons.com>

Hi Thomas,
Thomas Petazzoni wrote,

> Hello,
> 
> OK, -rc1 is released, so it's time to look at the build failures. Even
> though most developers should now be receiving direct e-mails, I guess
> it's still good to summarize where we are.
> 
> >         i686 |                    jamvm-2.0.0 | NOK | http://autobuild.buildroot.net/results/325a50d15e1836b31df4e84ba83b296abfb73041
> 
> init.c:22:18: fatal error: fenv.h: No such file or directory
> 
> Weird. <fenv.h> used to be available on i686. Waldemar, anything
> changed in uClibc in that regard?

This commit adds musl support via a patch:
0b6b67f34d6d4aeb340bbca579dbf85363c3f4ea

For fenv.h UCLIBC_HAS_FENV should be enabled in uClibc-ng config.
That is not the case.

I can't see why fenv.h would be installed in the past without
UCLIBC_HAS_FENV.

Without the patch, jamvm compiles fine.

best regards
 Waldemar

  parent reply	other threads:[~2016-11-06 19:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-06  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-11-05 Thomas Petazzoni
2016-11-06 13:39 ` Yegor Yefremov
2016-11-06 14:08   ` Thomas Petazzoni
2016-11-06 14:06 ` Thomas Petazzoni
2016-11-06 15:42   ` [Buildroot] -mcpu=native [was: Re: [autobuild.buildroot.net] Build results for 2016-11-05] Arnout Vandecappelle
2016-11-06 19:33   ` Waldemar Brodkorb [this message]
2016-11-06 21:22     ` [Buildroot] [autobuild.buildroot.net] Build results for 2016-11-05 Thomas Petazzoni
2016-11-06 22:48   ` Sam Bobroff
2016-11-11 20:41     ` Thomas Petazzoni
2016-11-07  4:12   ` Sam Bobroff
2016-11-07  8:28     ` Thomas Petazzoni
2016-11-07 18:25   ` Waldemar Brodkorb
2016-11-07 20:53     ` Thomas Petazzoni

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=20161106193346.GA27313@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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