Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Trevor Woerner <trevor.woerner@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3 v2] sanity.bbclass: Check for the known broken version of make
Date: Fri, 19 Jul 2013 10:41:20 +0100	[thread overview]
Message-ID: <2871747.3HkfyQL6od@helios> (raw)
In-Reply-To: <CALmOhgkONNQgOjYsosWAk2avLr2nEukjRW=kFuAzLMyyvjEuGA@mail.gmail.com>

On Tuesday 09 July 2013 16:14:55 Trevor Woerner wrote:
> On 8 July 2013 17:55, Mark Hatle <mark.hatle@windriver.com> wrote:
> > For anyone with an old or broken system, they will need to download (or
> > build) the buildtools..
> > install it and have it in their path prior to running oe-core.
> 
> Does a download location already exist with downloads available for
> people who receive this error when building? If so, could it be made
> part of the error message? Or maybe instead of asking people to use a
> working version of "make" the error message could instruct them to use
> one of these buildtools-tarball SDKs (and provide instructions for
> doing so)?

According to Beth, the current (nightly build) can be found here:

 http://autobuilder.yoctoproject.org/pub/nightly/CURRENT/buildtools/

Location for the upcoming 1.5 release when that is available:

 http://downloads.yoctoproject.org/releases/yocto/yocto-1.5/buildtools/

The tricky part is we don't have a solid location yet, only one being built 
from master. Perhaps we could link to an intermediary page with explanatory 
text that can link to the appropriate location.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-07-19  9:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 14:08 [PATCH 1/3 v2] sanity.bbclass: Check for the known broken version of make Mark Hatle
2013-06-27 14:21 ` Burton, Ross
2013-06-28 10:20   ` Paul Barker
2013-06-28 13:13     ` Mark Hatle
2013-06-28 15:11       ` Paul Barker
2013-06-28 18:22         ` Paul Barker
2013-06-30 15:56 ` Trevor Woerner
2013-06-30 16:02   ` Philip Balister
2013-06-30 22:55     ` Trevor Woerner
2013-07-08 16:55     ` Mark Hatle
2013-07-09 15:14       ` Trevor Woerner
2013-07-19  9:41         ` Paul Eggleton [this message]
2013-07-21 13:27           ` Trevor Woerner

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=2871747.3HkfyQL6od@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=trevor.woerner@linaro.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