From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/6] libtirpc: add host package
Date: Wed, 23 May 2018 07:58:05 +0200 [thread overview]
Message-ID: <20180523075805.3f93b462@windsurf> (raw)
In-Reply-To: <e1a18302-1cb8-40f7-f7b3-b5bcfa389075@mind.be>
Hello,
On Wed, 23 May 2018 00:21:05 +0200, Arnout Vandecappelle wrote:
> > +# Don't build anything for host; we only need the headers
> > +HOST_LIBTIRPC_CONFIGURE_CMDS = true
> > +HOST_LIBTIRPC_BUILD_CMDS = true
>
> Since we're not actually using any of the autotools (and since we can't,
> because rpcgen is missing), I'd make it a host-generic-package instead of
> host-autotools-package. There is at least one other package (can't remember
> which one) where we do this.
Indeed, this sounds like a good idea.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-23 5:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 10:30 [Buildroot] [PATCH v2 1/6] libtirpc: add host package Baruch Siach
2018-05-22 10:30 ` [Buildroot] [PATCH v2 2/6] nfs-utils: " Baruch Siach
2018-05-22 11:50 ` Baruch Siach
2018-05-22 21:07 ` Thomas Petazzoni
2018-05-22 10:30 ` [Buildroot] [PATCH v2 3/6] quota: depend on host-nfs-utils Baruch Siach
2018-05-22 10:30 ` [Buildroot] [PATCH v2 4/6] samba4: " Baruch Siach
2018-05-22 10:30 ` [Buildroot] [PATCH v2 5/6] autofs: " Baruch Siach
2018-05-22 10:30 ` [Buildroot] [PATCH v2 6/6] libtirpc: use rpcgen from host-nfs-utils Baruch Siach
2018-05-22 10:54 ` [Buildroot] [PATCH v2 1/6] libtirpc: add host package Thomas Petazzoni
2018-05-22 11:15 ` Baruch Siach
2018-05-22 22:21 ` Arnout Vandecappelle
2018-05-23 5:58 ` Thomas Petazzoni [this message]
2018-06-17 14:56 ` Peter Korsgaard
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=20180523075805.3f93b462@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.