Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jose Lamego <jose.a.lamego@linux.intel.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] bc: upgrade 1.06 to 1.07.1
Date: Fri, 19 May 2017 14:17:53 -0500	[thread overview]
Message-ID: <a2fd37e9-cc6d-b323-09d4-267dbdd0e5f5@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZEF_O3Evumo1+YQ8kpjt=FpTqszfg0704B45GXFHNYVA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1760 bytes --]



On 05/19/2017 10:25 AM, Burton, Ross wrote:
> 
> On 18 May 2017 at 23:28, Jose Lamego <jose.a.lamego@linux.intel.com
> <mailto:jose.a.lamego@linux.intel.com>> wrote:
> 
>     bc recipe must be upgraded to latest version in upstream.
> 
>     bc license changed from "GPLv2+ & LGPLv2.1" to "GPLv3+ & LGPLv3"
>     The new version exhibits a Parallel Make Race that required
>     unsetting PARALLEL_MAKE variable.
>     This change was tested with core-image-minimal in qemux86.
> 
> 
> It would be appreciated if you could spend a few minutes looking at what
> the build race is and pushing a fix upstream.  Or at least include a
> comment showing the failure.
> 
> I chased the sed thing as previous releases didn't need it: my build
> machine doesn't even have ed installed so HOSTTOOLS won't help.  This
> appears to be a regression as 1.06 shipped the file that needs ed to
> build.  The makefile now always builds a binary to generate a file that
> it then runs through ed, and it doesn't build this tool correctly in a
> cross environment either:
> 
> | /bin/bash: ./fbc: cannot execute binary file: Exec format error
> 
> (it's trying to run an arm binary on x86)
> 
> I'd suggest that we approach the upstream maintainer and discuss:
> 1) should the tarballs ship libmath.h instead of requiring it to be
> generated
> 2) using CC_FOR_BUILD etc from autoconf-archive to build fbc with the
> host compiler in cross-compile environments
> 3) can sed be used instead of ed to reduce the host requirements
> 
> Ross

Agree. I will contact the bc maintainer and work on the build race. I'll
get back to you with the findings. Thanks for the suggestions!

-- 
Jose Lamego | OTC Embedded Platforms & Tools | GDC


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]

  reply	other threads:[~2017-05-19 19:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 22:28 [PATCH 0/2] bc: upgrade 1.06 to 1.07.1 Jose Lamego
2017-05-18 22:28 ` [PATCH 1/2] conf/bitbake.conf: include ed in hosttools Jose Lamego
2017-05-18 23:12   ` Richard Purdie
2017-05-18 23:16     ` Khem Raj
2017-05-19  9:02       ` Anders Darander
2017-05-19 11:56         ` Burton, Ross
2017-05-19 13:01           ` Richard Purdie
2017-05-19 12:54         ` Jose Lamego
2017-05-19 15:47           ` Burton, Ross
2017-05-18 22:28 ` [PATCH 2/2] bc: upgrade 1.06 to 1.07.1 Jose Lamego
2017-05-19 15:25   ` Burton, Ross
2017-05-19 19:17     ` Jose Lamego [this message]
2017-07-20 21:24       ` Jose Lamego

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=a2fd37e9-cc6d-b323-09d4-267dbdd0e5f5@linux.intel.com \
    --to=jose.a.lamego@linux.intel.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox