All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Is the build system SCM sensitive?
Date: Mon, 27 Oct 2014 16:26:22 -0600	[thread overview]
Message-ID: <544EC68E.1090701@mlbassoc.com> (raw)
In-Reply-To: <CAJTo0Lb1SdFRQizn9dGGo45y-m5wPh9jd8C6KxYnkx-NvtJAPg@mail.gmail.com>

On 2014-10-27 14:07, Burton, Ross wrote:
>
> On 27 October 2014 19:40, Gary Thomas <gary@mlbassoc.com <mailto:gary@mlbassoc.com>> wrote:
>
>     I think I know what triggered this - a recent change in bitbake.conf
>     redefined BUILD_CPP (and others).  I had merged this change some six
>     hours before my strange build and had been building many other recipes
>     (also python with a similar set of dependencies) a number of times
>     before I touched the python-pygtk recipe.  Some dependency in that
>     recipe set off the rebuild storm that my other recipes had not.
>
>
> Ah yes, welcome back to master.  There's been stuff building up for a while.  :)
>
> This is where I point out that master between a release and M1 is known to be "volatile".  Whilst we obviously endeavour for it to be always buildable, deep and fundamental changes
> will be going in sooner rather than later.

This doesn't bother me - I expect it.  What took me by surprise
was when the behaviour radically changed from what I had seen
all day.  Totally explainable, but unexpected nonetheless.

>
> (ie this might be time to dust of my libexecdir-changing series)

Go for it :-)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


      reply	other threads:[~2014-10-27 22:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 16:50 Is the build system SCM sensitive? Gary Thomas
2014-10-27 18:03 ` Saul Wold
2014-10-27 19:40   ` Gary Thomas
2014-10-27 20:07     ` Burton, Ross
2014-10-27 22:26       ` Gary Thomas [this message]

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=544EC68E.1090701@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=ross.burton@intel.com \
    --cc=yocto@yoctoproject.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 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.