Why did you use the "internal nacl mailing list"? This is an issue that
affects all of Chromium. The NaCl team members are on chromium-dev, right?
If not, they should have been the day that our fates became intertwined.
J
On Tue, Oct 20, 2009 at 12:17 PM, John Grabowski <j...@chromium.org> wrote:
> I sent mail to the nacl team and got reassurances(at 1138AM) that they
> will hit it asap. I didn't cc chromium-dev because I used the internal nacl
> mailing list.
> jrg
>
>
> On Tue, Oct 20, 2009 at 12:15 PM, Scott Violet <s...@chromium.org> wrote:
>
>>
>> I want to say this bug has existed for around a week now. Is anyone
>> working on making it so that we don't need to explicitly set
>> GYP_DEFINES for the build to work again?
>>
>> -Scott
>>
>> On Tue, Oct 20, 2009 at 10:29 AM, Evan Martin <e...@chromium.org> wrote:
>> >
>> > (Since I've been contacted by a bunch people independently about this
>> > problem already, here's one mail to hopefully point others who have
>> > the same problem.)
>> >
>> > Though we auto-detect your system architecture when we build, for
>> > reasons opaque to me this doesn't work with nacl. I imagine someone
>> > is working on fixing it, but for now builds are broken.
>> >
>> > If you're getting errors like
>> > /usr/bin/ld: cannot find -lnpGoogleNaClPluginChrome
>> > and you're on a 64-bit system then you need to do one of
>> > 1) export GYP_DEFINES='target_arch=x64'
>> > 2) export GYP_DEFINES='disable_nacl=1'
>> >
>> > And then re-run gyp.
>> >
>> > >
>> >
>>
>>
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
