All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Linux kernel build dependency of 'bc'
Date: Thu, 06 Jun 2013 17:08:29 +0100	[thread overview]
Message-ID: <4045582.lhqZLrdHub@helios> (raw)
In-Reply-To: <CAP9ODKr9zNQENpsL_ASoKRWEfTauWhRx07Ps46=5u3D5=XXxng@mail.gmail.com>

Hi Otavio,

On Thursday 06 June 2013 12:11:04 Otavio Salvador wrote:
> I got a build failure in my auto builder; it has a very lean system install
> and it spot something it is new for me. It seems the kernel now depends on
> 'bc' util.
> 
> I tried to find a 'bc-native'  and couldn't find so I'd like to know if it
> is a known issue and if someone is already working in a 'bc-native' recipe
> to proper fix the issue.

We used to have bc in our list of required host packages in the Yocto Project 
quick start guide, but after some testing a few versions ago I removed it 
because it didn't seem to be needed. FWIW I don't have it installed on my 
primary build machine and I haven't noticed any problems as a result.

Rather than creating bc-native I think we should find out where the dependency 
on bc exists and try to patch it out (if practical); if it really is needed 
and too hard to remove, we can just add bc to the list of required host 
packages. I hope that's not the case though.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-06-06 16:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06 15:11 Linux kernel build dependency of 'bc' Otavio Salvador
2013-06-06 16:08 ` Paul Eggleton [this message]
2013-06-06 16:12   ` Chris Larson
2013-06-06 16:21     ` Otavio Salvador
2013-06-06 22:42 ` Bruce Ashfield

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=4045582.lhqZLrdHub@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.