Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libnss: fix build failures
Date: Sun, 16 Dec 2012 10:02:16 +0100	[thread overview]
Message-ID: <87d2yafjzb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1355232660-2377-1-git-send-email-gustavo@zacarias.com.ar> (Gustavo Zacarias's message of "Tue, 11 Dec 2012 10:31:00 -0300")

>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:

 Gustavo> Such as
 Gustavo> http://autobuild.buildroot.net/results/2ca1d135269a67201e6b4d995ce8fbe94db1ed3f

 Gustavo> The mozilla build system passes all of the different ways of CFLAGS
 Gustavo> (OPTIMIZER, XCFLAGS, OS_CFLAGS) even when building host tools
 Gustavo> (nsintall).
 Gustavo> The best way around this without patching libnss is just building the
 Gustavo> host tools first without any CFLAGS and then going on with the rest.

Committed, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-12-16  9:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 13:31 [Buildroot] [PATCH] libnss: fix build failures Gustavo Zacarias
2012-12-16  9:02 ` Peter Korsgaard [this message]
2012-12-16 10:10 ` 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=87d2yafjzb.fsf@dell.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