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 10:03:56 +0000 [thread overview]
Message-ID: <1374660286.28370.15.camel@firebird.rb.intel.com> (raw)
In-Reply-To: <CAOHjBZtoXxaHXFammidVFGwGQz6pCJBKhZe5233Us+bDQPQ9QQ@mail.gmail.com>
On Wed, 2013-07-24 at 11:43 +0200, Giuseppe Condorelli wrote:
> Hi Paul,
>
> I saw it early this morning (reading the previous thread)
> but I've not put it in the right attention I think.
> Now I've installed the sdk using that script and a run is still
> ongoing.
> I'll let you know.
> I ask the same to you: are you sure the FC17 and ahead have solved the
> make issue?
>
I'm running F19 and didn't ran into any problems.
I also have an F18 machine that works which has
make-3.82-14.fc18.x86_64 (this was the update that fixed the problem,
pushed two weeks ago).
And according to
https://admin.fedoraproject.org/updates/FEDORA-2013-11295/make-3.82-14.fc17?_csrf_token=9e2949b0095b56c00b217d0b00e77e28df2bb7ba
and
https://admin.fedoraproject.org/updates/make?_csrf_token=9e2949b0095b56c00b217d0b00e77e28df2bb7ba
the same patch was pushed for F17 make on the same day as F18, so that
should work too.
Cheers,
Stefan
> Many thanks,
> Cheers.
> Giuseppe
>
> 2013/7/24 Paul Barker <paul@paulbarker.me.uk>
> On 24 July 2013 09:47, Giuseppe Condorelli
> <giuseppe.condorelli@gmail.com> wrote:
> > Many thanks for the quick reply Stefan,
> >
> > For completion, I'm working on FC16.
> > Indeed (before sending the mail) I tried downloading the
> make rpm for FC17
> > (rpmfind.net) and to use it
> > (accordingly unpackaged under my personal directory,
> updating the PATH) with
> > the same failure.
> > Can this sound strange for you?
> > As you know, which are the make versions Fedora has released
> for the
> > FC17/18?
> >
> > I think at the moment the build of the buildtools-tarball
> will be the way
> > I'll follow, temporary disabling the sanity check.
> >
> > Cheers,
> > Giuseppe
> >
>
>
> As stated in a previous thread, there's a snapshot of the
> buildtools
> at
> http://autobuilder.yoctoproject.org/pub/nightly/CURRENT/buildtools/
> which might work for you. It should install a known good set
> of tools
> including make. This could be a good test for it.
>
> --
> Paul Barker
>
> Email: paul@paulbarker.me.uk
> http://www.paulbarker.me.uk
>
> _______________________________________________
> 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 10:04 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
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 [this message]
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=1374660286.28370.15.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