Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Zankel <chris@zankel.net>
To: buildroot
Subject: [PATCH 0/2] *** SUBJECT HERE ***
Date: Wed, 20 Nov 2013 14:02:36 -0800	[thread overview]
Message-ID: <cover.1384984956.git.chris@zankel.net> (raw)

Hi,

These two patches fix two of the broken builds for Xtensa:
- coreutils
- cdrkit

The first patch enables valloc for recent versions of uClibc (snapshot), which
is still used by cdrkit. The second patch disables libnsrp for Xtensa
(!BR_xtensa), which is used by libnss, and consequently libnss and ecryptfs.

Thanks,
-Chris

Chris Zankel (2):
  uclibc-snapshot: enable option UCLIBC_SUSV2_LEGACY
  libnspr: Add dependency on !BR2_xtensa

 package/ecryptfs-utils/Config.in      | 1 +
 package/libnspr/Config.in             | 3 ++-
 package/libnss/Config.in              | 1 +
 package/uclibc/uClibc-snapshot.config | 1 +
 4 files changed, 5 insertions(+), 1 deletion(-)

-- 
1.8.1.2

             reply	other threads:[~2013-11-20 22:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 22:02 Chris Zankel [this message]
2013-11-20 18:07 ` [PATCH 1/2] uclibc-snapshot: enable option UCLIBC_SUSV2_LEGACY Chris Zankel
2013-11-20 18:46 ` [PATCH 2/2] libnspr: Add dependency on !BR2_xtensa Chris Zankel

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=cover.1384984956.git.chris@zankel.net \
    --to=chris@zankel.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