Why then do you think vandebo and I hit this error? Or is this an error
from a subbuild whose result is ignored so the build otherwise works?
jrg
On Thu, Dec 10, 2009 at 9:31 AM, Gregory Dardyk <grego...@google.com> wrote:
> John,
> I build this target daily on Vista64, so I believe the problem is not
> caused by building on Vista alone. Also, disabling nacl won't help in this
> case - the flag does not disable the 64-bit targets. However, Chrome does
> not depend on the 64-bit targets at this stage, they are only built as part
> of 'all'. Therefore, you should be able to build Chrome successfully even if
> the 64-bit targets fail.
> Please let me know if you have any problems building the 64-bit Windows
> targets.
> Greg
>
> On Dec 9, 2009 10:28 PM, "John Grabowski" <j...@chromium.org> wrote:
>
> I saw this on Vista64 today as well. We don't have a Vista64 bot so it
> wouldn't have made the tree red.
>
> To fix, GYP_DEFINES='disable_nacl=1' gclient runhooks (in cygwin), then
> build.
>
> The right parties have been notified.
>
> jrg
>
> On Wed, Dec 9, 2009 at 2:00 PM, Steve VanDeBogart <vand...@chromium.org>
> wrote: > > My windows bui...
>
>
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
