Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] libnss: Add new package.
Date: Fri, 08 Jul 2011 16:17:02 +0200	[thread overview]
Message-ID: <877h7syi01.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CAFbHwiTz-KPomDTeSsn_s2Ax+YrT=Mo3r_udBs1Aig=Hv1EYrg@mail.gmail.com> (Will Newton's message of "Fri, 8 Jul 2011 14:27:30 +0100")

>>>>> "Will" == Will Newton <will.newton@gmail.com> writes:

Hi,

 Will> NSS is the Network Security Services library developed as part of
 Will> the Mozilla project. It provides similar functions to OpenSSL but
 Will> allows MPL, GPL and LGPL licensing.

 Will> +++ b/package/libnss/libnss-uclibc.patch
 Will> @@ -0,0 +1,19 @@
 Will> +
 Will> +uCLibc does not define RTLD_NOLOAD.
 Will> +
 Will> +Signed-off-by: Will Newton <will.newton@imgtec.com>
 Will> +
 Will> +--- nss-3.12.9.old/mozilla/security/nss/lib/freebl/stubs.c	2011-07-08
 Will> 13:32:54.964338355 +0100
 Will> ++++ nss-3.12.9/mozilla/security/nss/lib/freebl/stubs.c	2011-07-08
 Will> 13:33:57.255337490 +0100
 Will> +@@ -535,6 +535,11 @@
 Will> +     return SECSuccess;
 Will> + }
 Will> +
 Will> ++/* uClibc does not define RTLD_NOLOAD. */
 Will> ++#ifndef RTLD_NOLOAD
 Will> ++#define RTLD_NOLOAD 0
 Will> ++#endif

It's not completely true (but looks like a bug to me):

git grep RTLD_NOLOAD
libc/sysdeps/linux/common/bits/dlfcn.h:#define RTLD_NOLOAD      0x00004 /* Do no
libc/sysdeps/linux/mips/bits/dlfcn.h:#define RTLD_NOLOAD        0x00008 /* Do no

The common one is within #if 0 so that doesn't count, but for mips it
does. I suspect the best fix would actually be to fixup the mips header.

Thanks, I'll give it a bit of test and then commit.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2011-07-08 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08 13:27 [Buildroot] [PATCH v2] libnss: Add new package Will Newton
2011-07-08 14:17 ` Peter Korsgaard [this message]
2011-07-10 22:45 ` Peter Korsgaard

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=877h7syi01.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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