From: richard.purdie@linuxfoundation.org
To: "Martin Hundebøll" <martin@geanix.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] systemtap: Fix issues from 4.0 upgrade
Date: Wed, 17 Oct 2018 13:40:02 +0100 [thread overview]
Message-ID: <df1d6cd1dc275e9717cb297767a255ee70ae98aa.camel@linuxfoundation.org> (raw)
In-Reply-To: <bb016a11-6387-b7cd-4b64-7c8f925874fe@geanix.com>
On Wed, 2018-10-17 at 10:29 +0200, Martin Hundebøll wrote:
> On 16/10/2018 21.25, Richard Purdie wrote:
> > +
> > + # Fix makefile hardcoded path assumptions for systemd (assumes
> > $prefix)
> > + install -d `dirname ${D}${systemd_unitdir}`
> > + mv ${D}${prefix}/lib/systemd `dirname ${D}${systemd_unitdir}`
> > + rmdir ${D}${prefix}/lib --ignore-fail-on-non-empty
> > +
> > + # Ensure correct ownership for files copied in
> > + chown root.root ${D}${sysconfdir}/stap-exporter/* -R
>
> root:root ?
Well spotted, thanks!
Cheers,
Richard
prev parent reply other threads:[~2018-10-17 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 19:25 [PATCH] systemtap: Fix issues from 4.0 upgrade Richard Purdie
2018-10-17 8:29 ` Martin Hundebøll
2018-10-17 12:40 ` richard.purdie [this message]
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=df1d6cd1dc275e9717cb297767a255ee70ae98aa.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=martin@geanix.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