mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 3/3] host-systemd: Fix rpath space problem
Date: Tue, 31 Jul 2018 09:30:22 -0400	[thread overview]
Message-ID: <CAMwGMjw1b7Wka2VzCO5R7-=-eoeryUBJG66Ba--9yDp5PP-L5A@mail.gmail.com> (raw)
In-Reply-To: <20180731074900.jzgdn7mg6nadyp4g@pengutronix.de>

On Tue, Jul 31, 2018 at 3:49 AM Michael Olbrich
<m.olbrich@pengutronix.de> wrote:
>
> On Mon, Jul 30, 2018 at 12:58:09PM -0400, jon@ringle.org wrote:
> > From: Jon Ringle <jringle@gridpoint.com>
> >
> > Make room for chrpath manipulation in host-systemd.install.pack
> > The `-Drootprefix=/lib/..` adds sufficient space to avoids errors like:
> >
> > new rpath '${ORIGIN}/../../../lib' too large; maximum length 16
> > ptxdist: error: Failed to adjust rpath for '/home/local/GRIDPOINT/jringle/git/rootfs/platform-ec1c/packages/host-systemd-239/usr/lib/systemd/systemd'
> >
> > Signed-off-by: Jon Ringle <jringle@gridpoint.com>
> > ---
> >  rules/host-systemd.make | 16 +---------------
> >  1 file changed, 1 insertion(+), 15 deletions(-)
> >
> > diff --git a/rules/host-systemd.make b/rules/host-systemd.make
> > index 7f97a75..341daeb 100644
> > --- a/rules/host-systemd.make
> > +++ b/rules/host-systemd.make
> > @@ -23,6 +23,7 @@ HOST_PACKAGES-$(PTXCONF_HOST_SYSTEMD) += host-systemd
> >  HOST_SYSTEMD_CONF_TOOL       := meson
> >  HOST_SYSTEMD_CONF_OPT        := \
> >       $(HOST_MESON_OPT) \
> > +     -Drootprefix=/lib/.. \
> >       -Dacl=false \
> >       -Dadm-group=true \
> >       -Dapparmor=false \
> > @@ -120,19 +121,4 @@ HOST_SYSTEMD_CONF_OPT    := \
> >       -Dxz=false \
> >       -Dzlib=false
> >
> > -HOST_SYSTEMD_MAKE_OPT := systemd-hwdb
> > -
> > -# ----------------------------------------------------------------------------
> > -# Install
> > -# ----------------------------------------------------------------------------
> > -
> > -$(STATEDIR)/host-systemd.install:
> > -     @$(call targetinfo)
> > -     @rm -rf $(HOST_SYSTEMD_PKGDIR)
> > -     @install -vD -m755 $(HOST_SYSTEMD_DIR)-build/systemd-hwdb \
> > -             $(HOST_SYSTEMD_PKGDIR)/bin/systemd-hwdb
> > -     @install -vD -m755 $(HOST_SYSTEMD_DIR)-build/src/shared/libsystemd-shared-$(HOST_SYSTEMD_VERSION).so \
> > -             $(HOST_SYSTEMD_PKGDIR)/lib/libsystemd-shared-$(HOST_SYSTEMD_VERSION).so
> > -     @$(call touch)
> > -
>
>
> Why do you remove this? Currently only systemd-hwdb is needed, so why build
> anything else?

I am creating a host package version of my own project so I can run
the unit tests I have for it. This package requires the systemd
headers and libs.

-Jon

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-07-31 13:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 16:58 [ptxdist] [PATCH 1/3] hostapd: bool => tristate jon
2018-07-30 16:58 ` [ptxdist] [PATCH 2/3] HOST_MESON_OPT: Add --libdir jon
2018-07-30 16:58 ` [ptxdist] [PATCH 3/3] host-systemd: Fix rpath space problem jon
2018-07-31  7:49   ` Michael Olbrich
2018-07-31 13:30     ` Jon Ringle [this message]
2018-07-31 13:53       ` Michael Olbrich
2018-07-31 14:27         ` Jon Ringle
2018-08-01  7:17           ` Michael Olbrich

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='CAMwGMjw1b7Wka2VzCO5R7-=-eoeryUBJG66Ba--9yDp5PP-L5A@mail.gmail.com' \
    --to=jon@ringle.org \
    --cc=ptxdist@pengutronix.de \
    /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