On Wed, Sep 30, 2009 at 2:21 PM, Lei Zhang <[email protected]> wrote:
>
> On Wed, Sep 30, 2009 at 2:06 PM, spotrh <[email protected]> wrote:
>> On 09/30/2009 04:34 PM, Lei Zhang wrote:
>>> On Wed, Sep 30, 2009 at 11:23 AM, spotrh <[email protected]> wrote:
>>>> On 09/30/2009 01:58 PM, Lei Zhang wrote:
>>>>> Have you tried installing glibc-devel/i586?
>>>>
>>>> No, because the resulting binaries wouldn't really be x86_64, would they? 
>>>> :)
>>>
>>> Native client is trying to build 32-bit binaries, even on x86_64. All
>>> they do is generate some header files, which shouldn't change very
>>> often. I asked the NaCl folks to just check in a pre-generated header
>>> and stop building the 32-bit binaries in question.
>>
>> That would be perfect, thanks!
>>
>> ~spot
>>
>
> I filed a bug so this doesn't get dropped:
> http://code.google.com/p/nativeclient/issues/detail?id=104

It would be nice when we land stuff like NaCl that there's an easy way
for people to disable it -- I couldn't build at all yesterday due to
its landing, and we broke both Fedora and Ubuntu as well.  I
appreciate it's hard to land that sort of thing, but perhaps a staged
rollout (like: put the files in the tree, send out a note saying "hey,
try building the new target foobar before we make it a required
dependency!") would help.

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to