Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Denys Dmytriyenko <denis@denix.org>,
	openembedded-core@lists.openembedded.org
Cc: Denys Dmytriyenko <denys@ti.com>
Subject: Re: [PATCH] at: explicitly depend on bison-native for deterministic builds
Date: Tue, 09 Jan 2018 23:11:56 +0000	[thread overview]
Message-ID: <1515539516.29722.106.camel@linuxfoundation.org> (raw)
In-Reply-To: <1515536661-51529-1-git-send-email-denis@denix.org>

On Tue, 2018-01-09 at 17:24 -0500, Denys Dmytriyenko wrote:
> From: Denys Dmytriyenko <denys@ti.com>
> 
> Usually bison-native gets into sysroot through indirect dependencies,
> even with RSS. But when bison-native is not in sysroot, due to
> different
> system config,

Any idea what that "different system config" is?

I get worried about things like this and would like to understand it a
little better...

Cheers,

Richard




  reply	other threads:[~2018-01-09 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 22:24 [PATCH] at: explicitly depend on bison-native for deterministic builds Denys Dmytriyenko
2018-01-09 23:11 ` Richard Purdie [this message]
2018-01-10  1:33   ` Denys Dmytriyenko

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=1515539516.29722.106.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=denis@denix.org \
    --cc=denys@ti.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