Mirwangsir / gyp

Automatically exported from code.google.com/p/gyp
0 stars 0 forks source link

build error : 'file' is not defined #428

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. cd trunk
2. ninja -C out/Debug (or Release ; or when not using ninja, 'make all'

What is the expected output? What do you see instead?
Instead of compilation success, I have : 

ACTION Running source/patched-yasm/modules/arch/x86/gen_x86_insn.py out/Debug/obj/gen/third_party/yasm/x86insns.c Traceback (most recent call last): File "source/patched-yasm/modules/arch/x86/gen_x86_insn.py", line 8334, in output_groups(file(os.path.join(out_dir, "x86insns.c"), "wt")) NameError: name 'file' is not defined third_party/yasm/generate_files.host.mk:13: recipe for target 'out/Debug/obj/gen/third_party/yasm/x86insns.c' failed make: *\ [out/Debug/obj/gen/third_party/yasm/x86insns.c] Error 1


What version of the product are you using? On what operating system?
I'm running Archlinux x86_64

Please provide any additional information below.
I'm not sure what is happening here : seems like the 'file' variable or 
function in 'file(os.path.....' is not defined.

Original issue reported on code.google.com by nico...@smartmeup.org on 21 May 2014 at 8:01

GoogleCodeExporter commented 9 years ago
Okay i solved that problem, in case anyone is interested : Archlinux had 
decided to switch to **python 3** by default, so /usr/bin/python points toward 
python3 which is not what is needed by libjingle.

So what I did (as a temporary measure, I'm aware, but it worked) is ln -s 
/usr/bin/python /usr/bin/python2 for the build process.

Original comment by nico...@smartmeup.org on 21 May 2014 at 12:49