From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-04-25
Date: Mon, 21 May 2018 20:10:24 +0200 [thread overview]
Message-ID: <871se4khgv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CANQCQpaJZaMHUjskdyeb4tbWMtkghBtctgnm696bVsct1m=vkw@mail.gmail.com> (Matthew Weber's message of "Mon, 21 May 2018 10:05:12 -0500")
>>>>> "Matthew" == Matthew Weber <matthew.weber@rockwellcollins.com> writes:
Hi,
>> Hmm, I don't really feel confident adding patches that upstream find too
>> scary. What is the alternative? Does this only affect libnss on
>> Microblaze?
> Correct, only libnss on Microblaze. Romain had suggested adding a GCC
> bug for it instead. (ie like BR2_TOOLCHAIN_HAS_GCC_BUG_64735)
I think that is the best solution, yes. libnss luckily does not have a
lot of reverse dependencies.
Will you send a patch?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-05-21 18:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-04-25 Thomas Petazzoni
2018-04-29 22:15 ` Romain Naour
2018-04-30 7:15 ` Thomas Petazzoni
2018-04-30 8:17 ` Romain Naour
2018-05-09 10:21 ` Romain Naour
2018-05-10 13:24 ` Matthew Weber
2018-05-20 20:42 ` Peter Korsgaard
2018-05-21 15:05 ` Matthew Weber
2018-05-21 18:10 ` Peter Korsgaard [this message]
2018-05-21 18:21 ` Matthew Weber
2018-05-21 20:30 ` Matthew Weber
2018-05-08 13:23 ` Matthew Weber
2018-05-09 9:48 ` Romain Naour
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=871se4khgv.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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