All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Steve Pavao <stevep@korgrd.com>
Cc: yocto@yoctoproject.org
Subject: Re: advice on recipe for shared lib mDNSResponder
Date: Fri, 29 Sep 2017 11:30:54 +1300	[thread overview]
Message-ID: <13953290.7vapLMCcyK@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <1A69A446-50D3-4FE2-AC3E-4B26099B9EB5@korgrd.com>

Hi Steve,

On Friday, 29 September 2017 5:29:32 AM NZDT Steve Pavao wrote:
> I was unable to successfully build that recipe here, though.  I’ll check
> with the maintainers to ask why.
> 
> All I did was clone the meta-intel-iot-middleware repo, add that layer to
> bblayers.conf, and add mdns to IMAGE_INSTALL_append to get this far.

FYI the meta-intel-iot-middleware repository is no longer being actively
maintained, however coincidentally I am currently in the process of updating
and moving the useful pieces elsewhere. mdns wasn't on my list, however I have
just tried to fix it up, here is what I have so far:

http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-iot-middleware/commit/?h=paule/mdns-upgrade-1&id=7389dd6b1d3e69a05b8fa62673ba03b2a91073ff

Unfortunately I hit a linking issue - the dns-sd binary gets linked to the
unversioned libdns_sd.so symlink, which (correctly) is packaged in the -dev
package, but as a result you get a do_package_qa failure (and probably
runtime issues). Moving the .so symlink into the main package wouldn't be
the right thing to do, so the fix should be made elsewhere. I don't have
any more time to poke at it but I'm guessing it's not that hard to fix if
you're familiar with this kind of problem. (The issues we've been dealing with
here are unfortunately par for the course when building makefile-only
software.)

I'd probably recommend going the avahi route as suggested by Ross in his
reply, but if you absolutely need mDNSResponder then maybe this will get you
some way towards that.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2017-09-28 22:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27 22:58 advice on recipe for shared lib mDNSResponder Steve Pavao
2017-09-27 23:17 ` Andre McCurdy
2017-09-28 16:29   ` Steve Pavao
2017-09-28 22:30     ` Paul Eggleton [this message]
2017-09-29  0:11       ` Andre McCurdy
2017-09-29  0:44         ` Andre McCurdy
2017-09-29  1:14           ` Paul Eggleton
2017-09-28  9:38 ` Burton, Ross

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=13953290.7vapLMCcyK@peggleto-mobl.ger.corp.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=stevep@korgrd.com \
    --cc=yocto@yoctoproject.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.