Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH 1/1] mdns: move from meta-intel-iot-middleware
Date: Tue, 17 Oct 2017 14:09:32 -0400	[thread overview]
Message-ID: <20171017180932.GF9221@denix.org> (raw)
In-Reply-To: <CAMKF1sqfVVcvf6Hz9tPF7xobT-P64z16mbTQNQ9+t=-kSwo2-A@mail.gmail.com>

On Tue, Oct 17, 2017 at 10:01:13AM -0700, Khem Raj wrote:
> On Tue, Oct 17, 2017 at 9:58 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > I agree with Khem, I've merged oprofile even when it fails with musl,
> > because that was the main reason for moving it from oe-core to meta-oe, but
> > we don't want to burden Khem with more new musl issues when they are
> > detected soon enough (my world builds don't use musl, so I depend on Khem to
> > provide feedback when he can) .
> >
> > On Tue, Oct 17, 2017 at 6:23 PM, Khem Raj <raj.khem@gmail.com> wrote:
> >>
> >> On Mon, Oct 16, 2017 at 10:11 PM, Denys Dmytriyenko <denis@denix.org>
> >> wrote:
> >> > On Mon, Oct 16, 2017 at 09:19:25PM -0700, Khem Raj wrote:
> >> >> On Wed, Oct 4, 2017 at 1:20 PM, Paul Eggleton
> >> >> <paul.eggleton@linux.intel.com> wrote:
> >> >> > The following improvements have been made over the recipe that was in
> >> >> > meta-intel-iot-middleware (a layer which is no longer actively
> >> >> > maintained):
> >> >> >
> >> >> > * Upgrade to latest upstream version (765.50.9)
> >> >> > * Fix compilation failures by passing CC and LD
> >> >> > * Fix "no GNU hash in the ELF binary" issue
> >> >> > * Point S at the correct source subdirectory so that "make clean"
> >> >> > works
> >> >> > * Fix lack of soname on libdns_sd.so leading to missing RDEPENDS QA
> >> >> > error
> >> >> > * Add SUMMARY
> >> >> >
> >> >>
> >> >>
> >> >> This has been accepted into master but it fails to build with musl
> >> >
> >> > Is musl a requirement for meta-oe?
> >>
> >> We have fixed it to a point where we have around 10-12 recipes which
> >> don't compile
> >> with musl, and it would be better to keep this level as such and
> >> especially when we
> >> know its failing. its a requirement for oe-core
> 
> I do world builds on master-next with musl on qemumips and rpi3
> continuously, with a known set of failures, if a new one shows up
> I tend to report.

Ok, no problem, it's just demanding someone new, submitting a patch/recipe, to 
go fix musl, which they probably never heard of, would result in never hearing 
from them again. :)

Anyway, I'll look into getting some musl coverage for my submission as well...

-- 
Denys


  parent reply	other threads:[~2017-10-17 18:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04 20:20 [meta-networking][PATCH 0/1] mdns: move from meta-intel-iot-middleware Paul Eggleton
2017-10-04 20:20 ` [meta-networking][PATCH 1/1] " Paul Eggleton
2017-10-17  4:19   ` Khem Raj
2017-10-17  5:11     ` Denys Dmytriyenko
2017-10-17 16:23       ` Khem Raj
2017-10-17 16:58         ` Martin Jansa
2017-10-17 17:01           ` Khem Raj
2017-10-17 17:23             ` Joe MacDonald
2017-10-17 17:41               ` Khem Raj
2017-10-17 18:01                 ` Andre McCurdy
2017-10-17 19:00                   ` Khem Raj
2017-10-17 18:09             ` Denys Dmytriyenko [this message]
2017-10-17 19:05               ` Khem Raj
2017-10-17 21:01                 ` 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=20171017180932.GF9221@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --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