Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jukka Rissanen <jukka.rissanen@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] connman: Enable automake dependency tracking
Date: Mon, 04 May 2015 08:52:37 +0300	[thread overview]
Message-ID: <1430718757.2652.61.camel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LYtz5=Onm6ERW1fomWViwLNpWtaGnPZUYEfE53YNBsRmw@mail.gmail.com>

Hi Ross,

On pe, 2015-05-01 at 15:03 +0100, Burton, Ross wrote:
> 
> On 1 May 2015 at 12:41, Jukka Rissanen
> <jukka.rissanen@linux.intel.com> wrote:
>         The automake option --disable-dependency-tracking does not
>         work nicely
>         with ConnMan 1.29 release.
>         The reason is ConnMan commits
>         ac332c5d01b0737c18cb58c8ccc67cf6b0427e1d
>         and ea6c21b0b20f6f25b25386285d81d859dc843820 that change how
>         and when
>         various .in files are generated. After those commits, the auto
>         generated files / directories are created during compilation.
>         Earlier
>         they were generated by configure script.
> 
> 
> Yesterday I fixed this the other way: by adding mkdir calls to connman
> so that instead of requiring dependency tracking to be on so that
> directories are generated, the build makes the directories as
> required.
> 
> 
> 970e0ae was where dependency tracking was disabled on the rationale
> that it's slower, has races, and theoretically won't give us an
> advantage as we don't generally rebuild the same source tree
> repeatedly.

Ok, that makes sense.

> 
> 
> I'll submit my fix to connman in a moment.

Thanks, the connman patch looks good to me.


Cheers,
Jukka





      reply	other threads:[~2015-05-04  5:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 11:41 [PATCH] connman: Enable automake dependency tracking Jukka Rissanen
2015-05-01 14:03 ` Burton, Ross
2015-05-04  5:52   ` Jukka Rissanen [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=1430718757.2652.61.camel@linux.intel.com \
    --to=jukka.rissanen@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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