build error on windows with ninja

[Roger Tawa]

Hi all,

After syncing to ToT this morning, I am getting the following error when building (windows with ninja):

ninja: Entering directory `out/Debug'

...

[3877/11935] ACTION Generating yasm ve...ile: gen/third_party/yasm/version.mac.

FAILED: C:\src\depot_tools\python_bin\python.exe gyp-win-tool action-wrapper env

ironment.x86 generate_files_target_generate_version_5085256bfc167d6d9e5b2a85fb85

0441..rsp

Version tokenizing error

...

ninja: build stopped: subcommand failed.

The generated file contains:

call "..\..\third_party\cygwin\setup_env.bat" && set CYGWIN=nontsec && bash -c "cd ../../third_party/yasm ; '../../out/Debug/genversion' '../../out/Debug/gen/third_party/yasm/version.mac'"

Any ideas?

Thanks,
Roger

-

[Miranda Callahan]

Same error on Ubuntu, FWIW.

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Joao da Silva]

I had this problem earlier this morning and I've pinged @hbono.

To fix it locally, edit

third_party/yasm/source/patched-yasm/modules/preprocs/nasm/genversion.c

 and replace PACKAGE_VERSION with PACKAGE_INTVER.

- Joao

[Stefan Kuhne]

Just checking - is someone fixing this?

On Fri, Nov 16, 2012 at 6:35 AM, Joao da Silva <joaod...@chromium.org> wrote:

third_party/yasm/source/patched-yasm/modules/preprocs/nasm/genversion.c

[Stefan Kuhne]

After fixing that it continues:

In file included from ../../third_party/WebKit/Source/WebCore/accessibility/atk/WebKitAccessibleInterfaceHypertext.cpp:21:0:

../../third_party/WebKit/Source/WebCore/accessibility/atk/WebKitAccessibleInterfaceHypertext.h:23:21: fatal error: atk/atk.h: No such file or directory

compilation terminated.

I already updated the dependencies. Any ideas about that?

Cheers!

-Stefan

[Roger Tawa]

I'm no longer getting this problem, even though I removed Joao patch (thanks for that btw).  I am synced to rev 168179.

Thanks,
Roger

-

[Xiaohan Wang (王消寒)]

I just synced to r168239 and I am seeing the same error on Linux. Followed joaodasilv@'s tip and it worked. 

[Elliot Glaysher (Chromium)]

I am still having this problem, synced to r168305.

[Jeremy Apthorp]

I'm still seeing this as of r168486, on ninja on windows.

[Nico Weber]

In general, it's useful to file a bug for build problems.

I tried to reproduce this with a chromeos bug last friday and couldn't
see it. Does it reproduce reliably on windows? Can someone who's
seeing it bisect and find out when it was introduced?

Nico

[Jeremy Apthorp]

I removed my out/ directory and rebuilt, and the error went away. ¯\(°_o)/¯