On Thu, Oct 15, 2009 at 9:04 PM, Michael Moss <[email protected]> wrote:
> > On Thu, Oct 15, 2009 at 8:59 PM, Fumitoshi Ukai (鵜飼文敏) > <[email protected]> wrote: > > On x86_64 machine, I couldn't build even if I clobber.. > > > > /usr/bin/ld: skipping incompatible > > > /usr/local/google/home/ukai/src/chromium1/src/sconsbuild/Release/lib/libnpGoogleNaClPluginChrome.a > > when searching for -lnpGoogleNaClPluginChrome > > /usr/bin/ld: cannot find -lnpGoogleNaClPluginChrome > > collect2: ld returned 1 exit status > > > > Is this known issue? > > It is fine with GYP_DEFINES="target_arch=ia32", of course. > > I haven't looked into it yet, but NaCl apparently has it's own notion > of target_arch. For now, the best bet is probably explicitly setting > GYP_DEFINES as you're doing. > > Michael > You can also disable NaCl with disable_nacl=1 in GYP_DEFINES. Antoine > > > > On Fri, Oct 16, 2009 at 9:28 AM, Michael Moss <[email protected]> > wrote: > >> > >> http://codereview.chromium.org/271113 may require a clobber for Linux > >> builds. The default build used to be 32-bit, but it will now be > >> whatever your build host architecture is. If you are on a 64-bit > >> machine, and haven't explicitly been setting 'target_arch' in gyp, > >> your build will switch from 32-bit to 64-bit. If this breaks anything, > >> clobbering or moving your existing build directory should fix it. > >> > >> If you want to continue building 32-bit on 64-bit hosts, you can force > >> it by setting GYP_DEFINES="target_arch=ia32" in the environment. > >> > >> Michael > >> > >> >> > >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
