From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, Kristian Amlie <kristian.amlie@mender.io>
Cc: OE-core <Openembedded-core@lists.openembedded.org>
Subject: Re: go-bootstrap / go-native conflict during do_rootfs
Date: Mon, 20 Mar 2017 15:17:19 +0000 [thread overview]
Message-ID: <1490023039.13980.142.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1sp6C9qqzt1azPQwOpxySj34_KifVosn5aSp2bzDjfoS6w@mail.gmail.com>
On Mon, 2017-03-20 at 07:49 -0700, Khem Raj wrote:
> On Mon, Mar 20, 2017 at 6:47 AM, Kristian Amlie
> <kristian.amlie@mender.io> wrote:
> >
> > --------------------------------------------------
> >
> > Additionally, in the logs I found these two snippets:
> >
> > --------------------------------------------------
> > Considering setscene task: ['go-native', 'do_populate_sysroot']
> > considering dependency: ['go-native', 'do_populate_sysroot']
> > considering dependency: ['mender-artifact-native',
> > 'do_populate_sysroot']
> > Adding dependency on go-native
> > ...
> > Considering setscene task: ['go-bootstrap-native',
> > 'do_populate_sysroot']
> > considering dependency: ['go-native', 'do_populate_sysroot']
> > Adding dependency on go-bootstrap-native
> > --------------------------------------------------
> >
> > which lead me to believe that all dependencies are being pulled in
> > simultaneously by do_rootfs, but go-native and go-bootstrap-native
> > are
> > in fact mutually exclusive, since they install to the sysroot in
> > the
> > same location. Note that both compilers build just fine, it's only
> > at
> > the do_rootfs stage that this shows up.
> >
> > I think the oe-meta-go layer solved this by having go-bootstrap-
> > native
> > install in a different location, but I'm unsure what is the best
> > approach for OE.
> go-bootstrap is only needed for few recipes. I think we should find
> out
> a way to keep this dep limited to those recipes and not reflect in
> final
> image rootfs creation. That seems to be not useful.
There is code in sstate.bbclass in setscene_depvalid:
# Consider sysroot depending on sysroot tasks
if taskdependees[task][1] == 'do_populate_sysroot' and taskdependees[dep][1] == 'do_populate_sysroot':
[...]
# Nothing need depend on libc-initial/gcc-cross-initial
if "-initial" in taskdependees[task][0]:
continue
so if go-bootstrap-native were renamed go-native-initial, things might
happen to work better...
Cheers,
Richard
next prev parent reply other threads:[~2017-03-20 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 13:47 go-bootstrap / go-native conflict during do_rootfs Kristian Amlie
2017-03-20 14:49 ` Khem Raj
2017-03-20 15:17 ` Richard Purdie [this message]
2017-03-20 15:29 ` Khem Raj
2017-03-20 16:50 ` Khem Raj
2017-03-21 6:13 ` Kristian Amlie
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=1490023039.13980.142.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=kristian.amlie@mender.io \
--cc=raj.khem@gmail.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