From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/sysrepo: fix host/staging install steps
Date: Tue, 5 Nov 2019 09:09:31 +0100 [thread overview]
Message-ID: <20191105090931.5b8953c9@windsurf> (raw)
In-Reply-To: <CAEyMn7bdb24JJnVQMa+Tr_uBQU3vHEdcnj6vxEMewr3oADXfrA@mail.gmail.com>
On Tue, 5 Nov 2019 09:03:27 +0100
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> The problem comes from the hardcoded TARGET_DIR that is compiled-in the
> needed host tools (sysrepocfg, sysrepoctl) in the build host step.
> This value is used
> as target for this tools as well as search path for other dependencies.
> With this all install steps tries to install parts into that
> TARGET_DIR. I think it is not
> really clean that this happens. When I just do the part hat only the
> tools are build in
> the host step. Then the staging will fail because there are missing
> files that are
> expected to be located in the TARGET_DIR. The tools have the hardcoded search
> path set to the TARGET_DIR.
Hum, OK. Did you talk about this with the upstream project ?
Your proposed solution is probably good as a workaround, but long term
it would be nice to have the upstream sysrepo project support better
cross-compilation, by solving those paths issues.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-05 8:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 6:01 [Buildroot] [PATCH 1/1] package/sysrepo: fix host/staging install steps Heiko Thiery
2019-11-04 21:38 ` Thomas Petazzoni
2019-11-05 8:03 ` Heiko Thiery
2019-11-05 8:09 ` Thomas Petazzoni [this message]
2019-11-05 8:19 ` Heiko Thiery
2019-11-08 21:58 ` Thomas Petazzoni
2019-11-10 16:00 ` Heiko Thiery
2019-11-11 13:53 ` Thomas Petazzoni
2019-11-11 14:07 ` Heiko Thiery
2019-11-11 14:27 ` Thomas Petazzoni
2019-11-11 14:35 ` Heiko Thiery
2019-11-11 14:40 ` Thomas Petazzoni
2019-11-11 14:43 ` Heiko Thiery
2019-11-11 14:59 ` Thomas Petazzoni
2019-11-11 15:04 ` Heiko Thiery
2019-11-11 15:12 ` Thomas Petazzoni
2019-11-11 19:22 ` Heiko Thiery
2019-11-12 7:53 ` Heiko Thiery
2019-11-17 5:32 ` Heiko Thiery
2019-12-02 8:15 ` Heiko Thiery
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=20191105090931.5b8953c9@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.