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 1/2] package/iprutils: bump version to 2.4.10
Date: Sun, 7 Feb 2016 14:24:05 +0100	[thread overview]
Message-ID: <20160207142405.23351d1f@free-electrons.com> (raw)
In-Reply-To: <1454167529-26085-1-git-send-email-bernd.kuhls@t-online.de>

Dear Bernd Kuhls,

On Sat, 30 Jan 2016 16:25:28 +0100, Bernd Kuhls wrote:
> Upstream now provides a new autoconf-based build system, therefore
> our patches for Makefile are not needed anymore. The build system
> checks for function matherr in libm, this test fails so check for
> main().

Checking for main() is silly. Instead, I've changed the patch to check
for pow(), which is actually used by the iprconfig.c code. I've also
reformatted the patch with Git. Once again: whenever the upstream
project uses Git, *please* use Git to format the patches for that
package.

I also had to rework the gettext patch because the configure.ac script
was now checking for <libintl.h>, which doesn't exist in uClibc
toolchains if you haven't built gettext.

I've also submitted the two patches upstream.

Thanks!

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

      parent reply	other threads:[~2016-02-07 13:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-30 15:25 [Buildroot] [PATCH 1/2] package/iprutils: bump version to 2.4.10 Bernd Kuhls
2016-01-30 15:25 ` [Buildroot] [PATCH 2/2] package/iprutils: Fix musl build Bernd Kuhls
2016-02-02 16:01   ` Arnout Vandecappelle
2016-02-07 13:24   ` Thomas Petazzoni
2016-02-07 13:24 ` Thomas Petazzoni [this message]

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=20160207142405.23351d1f@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