From: Daniel Dickinson <cshored@cshore.thecshore.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Hints on submitting to OE-Core
Date: Fri, 17 Mar 2017 21:38:07 -0400 [thread overview]
Message-ID: <20170317213807.377236b9@danielf.thecshore.com> (raw)
In-Reply-To: <3a6a7bd6-a5e5-b139-bc2a-53d3b6b41da5@mlbassoc.com>
On Sat, 18 Mar 2017 02:21:30 +0100
Gary Thomas <gary@mlbassoc.com> wrote:
>
> Have you read this?
> http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
I hadn't read in detail yet (I've seen similar before and from
skimming, it's about mechanics of the process), but I was looking more
in terms of coding and/or style guidelines for the meat of the patch,
and/or hints/tips on getting things accepted from the point of view of
things other than mechanics of patch submission.
> >
> > Also, in the layers list I'll be asking about some build issues
> > that I don't see with a manual bitbake, that look like missing
> > preqs on a build server, unless the layer should be requesting
> > installation of host files somewhere.
>
> Some tools required by ${HOSTTOOLS} are missing:
> cpio chrpath gawk diffstat makeinfo
As mentioned these are openembedded.org autobuilds of submitted layers,
so I was kind of hoping there were something I could change in the
layer to make it work. I guess the build host or chroot is missing
packges.
Regards,
Daniel
next prev parent reply other threads:[~2017-03-18 1:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 23:55 Hints on submitting to OE-Core Daniel Dickinson
2017-03-18 1:21 ` Gary Thomas
2017-03-18 1:38 ` Daniel Dickinson [this message]
2017-03-18 2:17 ` Khem Raj
2017-03-18 2:36 ` Daniel Dickinson
2017-03-18 8:42 ` akuster808
2017-03-18 17:17 ` Daniel Dickinson
2017-03-18 19:05 ` Daniel Dickinson
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=20170317213807.377236b9@danielf.thecshore.com \
--to=cshored@cshore.thecshore.com \
--cc=gary@mlbassoc.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 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.