[chromium-dev] Re: [linux] how to work around nacl errors in 64-bit build
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 -~--~~~~--~~--~--~---
[chromium-dev] Re: [linux] how to work around nacl errors in 64-bit build
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 -~--~~~~--~~--~--~---
[chromium-dev] Re: [linux] how to work around nacl errors in 64-bit build
On Wed, Oct 21, 2009 at 11:37 AM, Jeremy Orlow jor...@chromium.org wrote: Why did you use the internal nacl mailing list? To keep things unambiguous and try for immediate action for a build-ish break. Only members can view list members for the public lists. I didn't want to join those lists just to confirm my mail would get sent to the right people. 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. I have no idea if nacl members are on chromium-dev. I didn't want to assume and have the problem drop on the floor. jrg --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: [linux] how to work around nacl errors in 64-bit build
I'll follow up with the NaCl team to make sure they are. On Wed, Oct 21, 2009 at 11:57 AM, John Grabowski j...@chromium.org wrote: On Wed, Oct 21, 2009 at 11:37 AM, Jeremy Orlow jor...@chromium.orgwrote: Why did you use the internal nacl mailing list? To keep things unambiguous and try for immediate action for a build-ish break. Only members can view list members for the public lists. I didn't want to join those lists just to confirm my mail would get sent to the right people. 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. I have no idea if nacl members are on chromium-dev. I didn't want to assume and have the problem drop on the floor. jrg --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: [linux] how to work around nacl errors in 64-bit build
To update, the issue will probably be resolved in gyp. Nacl has a bit of an unusual build configuration, but it should probably be supported. There is a discussion on the gyp developers list looking into the best way to accommodate it. Michael --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: [linux] how to work around nacl errors in 64-bit build
Michael, The variables handling in gyp definitely needs to be settled, but to get people going with this, I've sent you a change that should resolve this particular case (though it is moderately redundant). -BradN On Wed, Oct 21, 2009 at 12:58 PM, Michael Moss mm...@chromium.org wrote: To update, the issue will probably be resolved in gyp. Nacl has a bit of an unusual build configuration, but it should probably be supported. There is a discussion on the gyp developers list looking into the best way to accommodate it. Michael --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: [linux] how to work around nacl errors in 64-bit build
That's http://codereview.chromium.org/295044 for reference. On Wed, Oct 21, 2009 at 1:06 PM, Bradley Nelson bradnel...@google.comwrote: Michael, The variables handling in gyp definitely needs to be settled, but to get people going with this, I've sent you a change that should resolve this particular case (though it is moderately redundant). -BradN On Wed, Oct 21, 2009 at 12:58 PM, Michael Moss mm...@chromium.org wrote: To update, the issue will probably be resolved in gyp. Nacl has a bit of an unusual build configuration, but it should probably be supported. There is a discussion on the gyp developers list looking into the best way to accommodate it. Michael --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: [linux] how to work around nacl errors in 64-bit build
Awesome. Thanks! -Scott On Tue, Oct 20, 2009 at 12:19 PM, Michael Moss mm...@chromium.org wrote: I'm working on it. 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 -~--~~~~--~~--~--~---