search

joshua655 / v8cgi

Automatically exported from code.google.com/p/v8cgi
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

build fails on x64 system #72

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. try to cross build on any x64 linux
2.
3.

What is the expected output? What do you see instead?
 v8cgi build configuration needs to be in sync with v8 build:
  in v8 - gcc is configured to build for i386 target on all systems,
  in v8cgi - gcc uses the default target, which is x64 on 64-bit systems

What version of the product are you using? On what operating system?
 building 0.8.3dev on fedora9 x64

Please provide any additional information below.
 add -m32 to CCFLAGS ans LINKFLAGS

Original issue reported on code.google.com by romash...@gmail.com on 26 Aug 2010 at 3:19

GoogleCodeExporter commented 9 years ago 
Okay, this might be an additional scons build option.

Original comment by ondrej.zara on 27 Aug 2010 at 3:14

GoogleCodeExporter commented 9 years ago 
Could you make -m32 defaut and -m64 an option?
It looks like they screwed something in v8 build config -
nobody knows what happens when they fix it there.

Original comment by romash...@gmail.com on 27 Aug 2010 at 5:38

GoogleCodeExporter commented 9 years ago 
In my opinion, sticking with "default" behavior is the most logical one - and 
using a non-standard build options should require explicit command line switch. 
On the other hand, I agree that v8's build system is broken, because of this 
glitch.

Original comment by ondrej.zara on 28 Aug 2010 at 10:22

GoogleCodeExporter commented 9 years ago

Original comment by ondrej.zara on 28 Aug 2010 at 10:22

GoogleCodeExporter commented 9 years ago 
Abscence of target select option in your build configuration in 
only part of the problem.

The other part is that your default target (i.e. gcc defalt) and 
their default target (as returned by utils.GuessArchitecture()) 
are different on x64 systems.

It seems that their SConstruct is ok. Something is wrong with 
"utils.GuessArchitecture" that returns ia32 instead of x64
on my system.

Could you sync both configurations by using their setup?
They seem to do everything right in their script - it a bug 
in "utils", I think, that causes wrong target selection.

Adapting their build configuration would be preferrable because 
this will keep targets for v8 and v8cgi in sync (whether "utils" 
has the bug or not) and your build will then automatically 
provide additional options for target architectures.

Original comment by romash...@gmail.com on 29 Aug 2010 at 1:53

GoogleCodeExporter commented 9 years ago 
Trying to sync the V8 build process... 
http://groups.google.com/group/v8-users/browse_thread/thread/ac8c00ab23d074a1

Original comment by ondrej.zara on 1 Oct 2010 at 6:54