From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 03/11] libtirpc: add patches to fix a number of issues
Date: Tue, 13 Nov 2012 07:47:41 +0100 [thread overview]
Message-ID: <50A1ED0D.5020104@mind.be> (raw)
In-Reply-To: <56daf58a13bf6cc3b2e2f696c961c9f3a8de21ce.1352583641.git.thomas.petazzoni@free-electrons.com>
On 10/11/12 22:42, Thomas Petazzoni wrote:
> libtirpc-0005-rpcent-mark-getrpcbyname-name-argument-as-const-char.patch
> fixes build failures like
> http://autobuild.buildroot.org/results/7a3a751fe02c639ca75c575ca7fe20a72372b8d6/build-end.log.
>
> libtirpc-0006-rpcent-remove-prototypes-of-reentrant-variants.patch
> ensures that functions not implemented by libtirpc are not described
> in a header file. It also allows to remove those prototypes that were
> not matching the functions available in glibc or uClibc, causing
> mismatch in prototypes.
>
> libtirpc-0007-doc-Makefile.am-fix-out-of-tree-installation.patch is a
> minor fix.
>
> The following patches (8 to 9) allow libtirpc to provide sufficient
> things to be able to build rpcbind on top of it.
>
> All these patches have been submitted upstream on the libtirpc-devel@
> mailing list.
>
> Signed-off-by: Thomas Petazzoni<thomas.petazzoni@free-electrons.com>
After a quick browse:
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
(untested)
I would have split up the rpcbind things as a separate commit, but that's
a minor detail.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-11-13 6:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 21:42 [Buildroot] Fixes for RPC support Thomas Petazzoni
2012-11-10 21:42 ` [Buildroot] [PATCH 01/11] conntrack-tools: do not depend on BR2_INET_RPC and use libtirpc when available Thomas Petazzoni
2012-11-10 21:42 ` [Buildroot] [PATCH 02/11] libtirpc: remove patch numbers from patch titles Thomas Petazzoni
2012-11-10 21:42 ` [Buildroot] [PATCH 03/11] libtirpc: add patches to fix a number of issues Thomas Petazzoni
2012-11-13 6:47 ` Arnout Vandecappelle [this message]
2012-11-10 21:42 ` [Buildroot] [PATCH 04/11] libtirpc: handle the case where uClibc may have RPC support Thomas Petazzoni
2012-11-10 21:42 ` [Buildroot] [PATCH 05/11] nfs-utils: reformat patch set as git patches Thomas Petazzoni
2012-11-11 23:24 ` Arnout Vandecappelle
2012-11-10 21:42 ` [Buildroot] [PATCH 06/11] nfs-utils: add patches to allow compilation against libtirpc Thomas Petazzoni
2012-11-10 21:42 ` [Buildroot] [PATCH 07/11] quota: allow usage of getrpcbynumber() instead of getrpcbynumber_r() Thomas Petazzoni
2012-11-10 21:42 ` [Buildroot] [PATCH 08/11] rpcbind: convert to git patch Thomas Petazzoni
2012-11-10 21:42 ` [Buildroot] [PATCH 09/11] rpcbind: allow build without NSS support Thomas Petazzoni
2012-11-10 21:42 ` [Buildroot] [PATCH 10/11] libnetfilter_queue: does not build without IPv6 support Thomas Petazzoni
2012-11-10 21:42 ` [Buildroot] [PATCH 11/11] rpcbind: fix build on toolchains " Thomas Petazzoni
2012-11-14 22:02 ` [Buildroot] Fixes for RPC support 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=50A1ED0D.5020104@mind.be \
--to=arnout@mind.be \
--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.