From: "Stanacar, StefanX" <stefanx.stanacar@intel.com>
To: Giuseppe Condorelli <giuseppe.condorelli@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: How to solve the make 3.82 issue at sanity check time?
Date: Wed, 24 Jul 2013 07:47:39 +0000 [thread overview]
Message-ID: <1374652108.28370.6.camel@firebird.rb.intel.com> (raw)
In-Reply-To: <CAOHjBZuDPPjk9dySzOTtGjXzy5yisjdumag=22qV5U-aW2hj4A@mail.gmail.com>
On Wed, 2013-07-24 at 09:33 +0200, Giuseppe Condorelli wrote:
> Hi All,
>
> given that the make v. 3.82 is broken, as the sanity check highlights,
> which is the best solution
> to allow Fedora users (as I am) to go ahead with the build?
> I don't like to avoid sanity checks or to use an older version of
> sanity.bbclass.
> Please let me know, currently this issue is blocking for me.
>
Fedora pushed updates for make in F17 & 18 (19 wasn't broken afaik) so
you should just update your system. (yum update make should do the
trick).
Alternatively you can bitbake buildtools-tarball on an working system
(or disable the sanity check before, touch conf/sanity.conf) and install
that on your system (if you are on F16 which isn't updated anymore)
Cheers,
Stefan
> Cheers,
> Giuseppe
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2013-07-24 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 7:33 How to solve the make 3.82 issue at sanity check time? Giuseppe Condorelli
2013-07-24 7:47 ` Stanacar, StefanX [this message]
2013-07-24 8:47 ` Giuseppe Condorelli
2013-07-24 8:55 ` Paul Barker
2013-07-24 9:43 ` Giuseppe Condorelli
2013-07-24 10:03 ` Stanacar, StefanX
2013-07-25 7:40 ` Giuseppe Condorelli
2013-07-25 8:11 ` Guo Chunrong-B40290
2013-07-25 16:42 ` Khem Raj
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=1374652108.28370.6.camel@firebird.rb.intel.com \
--to=stefanx.stanacar@intel.com \
--cc=giuseppe.condorelli@gmail.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