From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Marcus Hoffmann <m.hoffmann@cartelsol.com>,
Robert Yang <liezhi.yang@windriver.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: systemd PACKAGECONFIG = "lz4" leads to broken init
Date: Thu, 21 Dec 2017 15:25:40 +0200 [thread overview]
Message-ID: <b1fae413-8def-fac0-8755-92319a0ff485@linux.intel.com> (raw)
In-Reply-To: <b3556d63-e844-a2cb-2e42-a9732ad68477@cartelsol.com>
On 12/21/2017 03:26 PM, Marcus Hoffmann wrote:
> thanks for the patch. I'd like to understand how this fixes the problem
> or probably more genrally how the PACKAGECONFIG thing works internally.
>
> Can someone give me a pointer on where to look? It seems a bit like
> magic just adding "lz4" twice at the end :-).
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PACKAGECONFIG
Alex
next prev parent reply other threads:[~2017-12-21 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 21:34 systemd PACKAGECONFIG = "lz4" leads to broken init Marcus Hoffmann
2017-12-21 4:40 ` Robert Yang
2017-12-21 13:26 ` Marcus Hoffmann
2017-12-21 13:25 ` Alexander Kanavin [this message]
2017-12-22 2:00 ` Robert Yang
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=b1fae413-8def-fac0-8755-92319a0ff485@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=liezhi.yang@windriver.com \
--cc=m.hoffmann@cartelsol.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