From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] host-libcap dependency on host-gperf
Date: Wed, 8 Feb 2017 13:00:08 +0100 [thread overview]
Message-ID: <20170208120008.npvfgnxknxclkuur@pengutronix.de> (raw)
In-Reply-To: <20170207170827.GA30572@archie.localdomain>
On Tue, Feb 07, 2017 at 06:08:27PM +0100, Clemens Gruber wrote:
> Hi,
>
> I noticed that the host-libcap package fails to build if host-gperf has
> not been built yet.
> There are two possible solutions:
> 1) Add a dependency to host-gperf (select HOST_GPERF in host-libcap.in?)
> 2) Add BUILD_GPERF=no to host-libcap's MAKE_OPTS.
From what I can tell, using gperf is just an optimization. So I think we
can use '2)' for host-libcap and '1)' for libcap.
> First I tried 1 but this does not seem to pull in host-gperf before
> building host-libcap. Is something like depends on HOST_GPERF necessary?
'select HOST_GPERF' should work. Did you run 'ptxdist oldconfig'
afterwards? You can also check the generated dependencies:
$ grep host-libcap platform-*/state/ptx_dgen_deps.post
You should see the deps on host-gperf here.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2017-02-08 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 17:08 Clemens Gruber
2017-02-08 12:00 ` Michael Olbrich [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=20170208120008.npvfgnxknxclkuur@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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