From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libnfs: Without native RPC use libtirpc
Date: Sun, 4 Oct 2015 14:35:05 +0300 [thread overview]
Message-ID: <20151004113505.GB2633@tarshish> (raw)
In-Reply-To: <CAGduivwirG_RD1LfYfgekqfEphCquOr5AG9H2WKB=4Vjv7OFnQ@mail.gmail.com>
Hi Maxime,
On Sat, Oct 03, 2015 at 04:25:30PM +0200, Maxime Hadjinlian wrote:
> There's a crappy file. Don't do git add with glob at home...
Or just do
echo '*.swp' >> .git/info/exclude
baruch
> On Sat, Oct 3, 2015 at 4:24 PM, Maxime Hadjinlian <
> maxime.hadjinlian at gmail.com> wrote:
> > Signed-off-by Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> > ---
> > RFC: A few packages uses libtirpc if there's no native RPC support *BUT*
> > they don't propagate the BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2.
> >
> > It was probably added later on in libtirpc, so the questions here, is
> > what do we do with that ? Should we add the dependencies to the other
> > packages ?
> > Do we need some kind of mechanisms to handle that ?
> > ---
> > package/libnfs/.Config.in.swp | Bin 0 -> 12288 bytes
> > package/libnfs/Config.in | 8 +++++---
> > package/libnfs/libnfs.mk | 4 ++++
> > 3 files changed, 9 insertions(+), 3 deletions(-)
> > create mode 100644 package/libnfs/.Config.in.swp
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-10-04 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 14:24 [Buildroot] [PATCH] libnfs: Without native RPC use libtirpc Maxime Hadjinlian
2015-10-03 14:25 ` Maxime Hadjinlian
2015-10-04 11:35 ` Baruch Siach [this message]
2015-10-04 13:42 ` Maxime Hadjinlian
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=20151004113505.GB2633@tarshish \
--to=baruch@tkos.co.il \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox