From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] libxmlrpc: bump to 1.39.11
Date: Sun, 4 Dec 2016 16:37:45 +0100 [thread overview]
Message-ID: <20161204163745.459990e3@free-electrons.com> (raw)
In-Reply-To: <20161204153328.GA27936@collins.gmr.ssr.upm.es>
Hello,
On Sun, 4 Dec 2016 16:33:28 +0100, Alvaro G. M. wrote:
> I already know the cause for this and the patch is simple. However, before
> sending the proposed patch as a git am commitable email, I'd like to query
> about which shall be the best way to provide it.
Sure. Thanks a lot for having already investigated the problem.
> The issue is that this version of libxmlrpc includes new subdir libutils++,
> which requires c++ but without which the library can perform its function
> perfectly. The way to solve this then is to patch lib/Makefile as inlined
> below, making this directory compilable only if there's c++ support.
>
> The question is: given that there is already a patch in buildroot called
> 0002-fix-non-cplusplus-build.patch which does exactly the same on a
> different file (lib/util/Makefile), should I modify this patch to include
> both changes, as the name and description of the patch is basically the
> same, or should I provide another .patch file for this to include under
> package/libxmlrpc?
Modifying the existing 0002-fix-non-cplusplus-build.patch is indeed the
right thing to do here.
Also, since you're interested in libxmlrpc, could you send the
different patches we have for this package to the upstream developers?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-12-04 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160825063044.CF4CA101E4C@stock.ovh.net>
2016-11-02 9:56 ` [Buildroot] [PATCH 1/1] Bump libxmlrpc Alvaro G. M
2016-11-02 22:26 ` Thomas Petazzoni
2016-11-03 6:13 ` Alvaro Gamez
2016-11-11 7:58 ` [Buildroot] [PATCH v2] Bump libxmlrpc to version 1.39.10 Alvaro G. M
2016-11-11 14:38 ` Thomas Petazzoni
2016-11-15 10:49 ` Alvaro Gamez
2016-11-15 10:50 ` [Buildroot] [PATCH v3 1/1] libxmlrpc: bump to 1.39.11 Alvaro G. M
2016-11-16 22:15 ` Thomas Petazzoni
2016-11-17 8:00 ` Alvaro Gamez
2016-12-04 14:06 ` Thomas Petazzoni
2016-12-04 15:33 ` Alvaro G. M.
2016-12-04 15:37 ` Thomas Petazzoni [this message]
2016-12-04 15:55 ` [Buildroot] [PATCH 1/1] libxmlrpc: fix build without C++ compiler Alvaro G. M
2016-12-04 20:49 ` Thomas Petazzoni
2016-12-04 16:18 ` [Buildroot] [PATCH v3 1/1] libxmlrpc: bump to 1.39.11 Alvaro G. M.
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=20161204163745.459990e3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.