Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 15:06:00 +0100	[thread overview]
Message-ID: <20161204150600.0bfe0ead@free-electrons.com> (raw)
In-Reply-To: <1479207044-12290-1-git-send-email-alvaro.gamez@hazent.com>

Hello,

On Tue, 15 Nov 2016 11:50:44 +0100, Alvaro G. M wrote:
> Previous version patches are still needed, but they have been
> upgraded to apply cleanly.
> 
> This also reverts aa9fde1c459dbc20b268694eafd7a1d3341dbf76, as that
> patch is already on upstream.
> 
> Signed-off-by: Alvaro Gamez <alvaro.gamez@hazent.com>
> ---
>  package/libxmlrpc/0001-fix-gennmtab-build.patch    |  2 +-
>  .../libxmlrpc/0004-use-correct-curl-config.patch   | 36 +++-------------------
>  package/libxmlrpc/0006-narrowing.patch             | 20 ------------
>  package/libxmlrpc/libxmlrpc.hash                   |  2 +-
>  package/libxmlrpc/libxmlrpc.mk                     |  4 +--
>  5 files changed, 9 insertions(+), 55 deletions(-)
>  delete mode 100644 package/libxmlrpc/0006-narrowing.patch

This update is causing a bunch of build failures:

  http://autobuild.buildroot.net/?reason=libxmlrpc-1.39.11

All of them look like this:

make[3]: Entering directory `/accts/mlweber1/rc-buildroot-test/scripts/instance-1/output/build/libxmlrpc-1.39.11/lib/libutil++'
/accts/mlweber1/rc-buildroot-test/scripts/instance-1/output/build/libxmlrpc-1.39.11/lib/libutil++/Makefile:109: depend.mk: No such file or directory
cat /dev/null >depend.mk
ln -s /accts/mlweber1/rc-buildroot-test/scripts/instance-1/output/build/libxmlrpc-1.39.11 srcdir
ln -s /accts/mlweber1/rc-buildroot-test/scripts/instance-1/output/build/libxmlrpc-1.39.11 blddir
make[3]: Leaving directory `/accts/mlweber1/rc-buildroot-test/scripts/instance-1/output/build/libxmlrpc-1.39.11/lib/libutil++'

Could you have a look and provide a patch to fix this?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  parent reply	other threads:[~2016-12-04 14:06 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 [this message]
2016-12-04 15:33               ` Alvaro G. M.
2016-12-04 15:37                 ` Thomas Petazzoni
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=20161204150600.0bfe0ead@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox