From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter Korsgaard <peter@korsgaard.com>
Date: Mon, 21 May 2018 20:10:24 +0200
Subject: [Buildroot] [autobuild.buildroot.net] Build results for
 2018-04-25
In-Reply-To: <CANQCQpaJZaMHUjskdyeb4tbWMtkghBtctgnm696bVsct1m=vkw@mail.gmail.com>
 (Matthew Weber's message of "Mon, 21 May 2018 10:05:12 -0500")
References: <20180426060013.EAB262079F@mail.bootlin.com>
 <18cd8156-03bc-05cf-5343-dec77dbf01a9@gmail.com>
 <20180430091509.3a9cdff2@windsurf>
 <cab2ab99-f53c-448f-7cdb-77456a189664@smile.fr>
 <56ce1d9d-7b2a-1cda-52e3-a01094e6713a@gmail.com>
 <CANQCQpZzeALsKx7GFMUD_jSSn+=YS9KZBoOeuf7dUR8Um1pJDQ@mail.gmail.com>
 <87zi0unjn5.fsf@dell.be.48ers.dk>
 <CANQCQpaJZaMHUjskdyeb4tbWMtkghBtctgnm696bVsct1m=vkw@mail.gmail.com>
Message-ID: <871se4khgv.fsf@dell.be.48ers.dk>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

>>>>> "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