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] uclibc-ng: update to 1.0.2
Date: Tue, 21 Apr 2015 13:32:20 +0200	[thread overview]
Message-ID: <20150421133220.4c819d7d@free-electrons.com> (raw)
In-Reply-To: <20150419140355.GA7043@waldemar-brodkorb.de>

Dear Waldemar Brodkorb,

On Sun, 19 Apr 2015 16:03:56 +0200, Waldemar Brodkorb wrote:
> Following problems found by buildroot should be fixed:
>  * static python2 compile (there is still a general problem, not related to uClibc-ng)
>  * postgresql configure hickup (link warnings got removed)
>  * samba runtime problems (RPATH in executables are respected)
> 
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
>  ...selection-better-do-it-in-your-build-syst.patch |   60 ----------------
>  .../0001-fix-static-linking-of-pthread-apps.patch  |   72 ++++++++++++++++++++
>  package/uclibc/Config.in                           |    2 +-
>  package/uclibc/uClibc-ng.config                    |    4 +-
>  package/uclibc/uclibc.hash                         |    2 +-
>  5 files changed, 77 insertions(+), 63 deletions(-)
>  delete mode 100644 package/uclibc/1.0.1/0001-remove-NAN-selection-better-do-it-in-your-build-syst.patch
>  create mode 100644 package/uclibc/1.0.2/0001-fix-static-linking-of-pthread-apps.patch

Applied, thanks.

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

      reply	other threads:[~2015-04-21 11:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-19 14:03 [Buildroot] [PATCH] uclibc-ng: update to 1.0.2 Waldemar Brodkorb
2015-04-21 11:32 ` 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=20150421133220.4c819d7d@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