All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Asselstine <mark.asselstine@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] systemd: disable 'libdir' QA check
Date: Mon, 12 Dec 2016 15:51:12 -0500	[thread overview]
Message-ID: <3629007.TMJVuC0a6H@tal> (raw)
In-Reply-To: <FE42CCA4-D2B8-4AE1-83E5-5CBE94FA160C@gmail.com>

On Monday, December 12, 2016 11:59:04 AM EST Khem Raj wrote:
> > On Dec 12, 2016, at 11:36 AM, Mark Asselstine
> > <mark.asselstine@windriver.com> wrote:
> > 
> > When building systemd with multilib support enabled in your build you
> > will get the following QA warnings (if the 'libdir' QA check is
> > enabled.)
> > 
> > WARNING: systemd-1_232-r0 do_package_qa: QA Issue: systemd-dbg: found \
> > library in wrong location: /lib/systemd/.debug/libsystemd-shared-232.so
> > systemd: found library in wrong location:
> > /lib/systemd/libsystemd-shared.so
> > systemd: found library in wrong location:
> > /lib/systemd/libsystemd-shared-232.so [libdir]
> Can we check if systemd can be a bit more flexible and accept it to go into
> multilib libdir ? this patch can be then applied if its not acceptable to
> systemd community.

I think the discussion I pointed to in the commit log closes the door on any 
such change. Specific the comment from Lennart --
https://github.com/systemd/systemd/issues/3810#issuecomment-235290526

They don't want the library to be found in the default search path, they want 
to maintain this as a "hidden, internal resource".

Being on the record that I am aware of this discussion/conclusion if I send a 
patch now I would look like a bit of ass for wasting their time. If someone 
else wants to push the issue, feel free. Unless there is a suitable 
recommendation that would satisfy their wishes and ours that I am missing.

Mark


> > Since systemd 231 upstream has included an 'internal' library which
> > they explicitly place in the application specific /lib/systemd
> > directory. You can see some of the discussion about this placement
> > here https://github.com/systemd/systemd/issues/3810
> > 
> > This placement is being picked up by the QA checker since when
> > multilibs are enabled it expects all libraries to be in lib32 or
> > lib64. Since the systemd and systemd-dbg packages don't contain any
> > other libraries we can respect the upstream placement and skip this QA
> > check for these packages. Unfortunately the QA mechanism doesn't allow
> > us to specify individual files so this approach is the best we can do.
> > 
> > Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
> > ---
> > meta/recipes-core/systemd/systemd_232.bb | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> > 
> > diff --git a/meta/recipes-core/systemd/systemd_232.bb
> > b/meta/recipes-core/systemd/systemd_232.bb index baee02e..c86badb 100644
> > --- a/meta/recipes-core/systemd/systemd_232.bb
> > +++ b/meta/recipes-core/systemd/systemd_232.bb
> > @@ -485,7 +485,8 @@ RRECOMMENDS_${PN} +=
> > "${@bb.utils.contains('PACKAGECONFIG', 'serial-getty-genera> 
> >                       os-release \
> > 
> > "
> > 
> > -INSANE_SKIP_${PN} += "dev-so"
> > +INSANE_SKIP_${PN} += "dev-so libdir"
> > +INSANE_SKIP_${PN}-dbg += "libdir"
> > INSANE_SKIP_${PN}-doc += " libdir"
> > 
> > PACKAGES =+ "udev udev-hwdb"




  parent reply	other threads:[~2016-12-12 20:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 19:36 [PATCH] systemd: disable 'libdir' QA check Mark Asselstine
2016-12-12 19:59 ` Khem Raj
2016-12-12 20:42   ` Burton, Ross
2016-12-12 20:51   ` Mark Asselstine [this message]
2016-12-12 21:17     ` Burton, Ross
2016-12-13 15:20       ` Mark Asselstine
     [not found]         ` <CAMKF1srzRaY=a+g3ntXHaVfq3yndZYF67aKGAa2odNSf=kzHpg@mail.gmail.com>
     [not found]           ` <CAMKF1spT3LkZmJLNVu7H61ZFeXo5o4mOqXi5v7ZWvML08ubAJw@mail.gmail.com>
2016-12-13 16:10             ` Khem Raj

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=3629007.TMJVuC0a6H@tal \
    --to=mark.asselstine@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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 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.