Yeah, I added those two libraries in and it compiled fine...however
now I get a segfault whenever mode code tries to compile some
Javascript (even a simple Hello World).

And yes, the shell sample linked fine.

On Sep 1, 5:49 am, Søren Gjesse <[email protected]> wrote:
> Looks as if you are missing tem libraries winmm.lib and ws2_32.lib when
> linking your application. Does the sample shell link OK (scons mode=debug
> sample=shell ...)?
>
> Regards,
> Søren
>
>
>
> On Wed, Sep 1, 2010 at 09:36, Corey <[email protected]> wrote:
> > Trying to build 32-bit on 64-bit Windows is turning into a nightmare.
> > Okay so, using static libraries just appears to give linking errors in
> > the application I'm trying to use it in:
>
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__timegett...@0 referenced in function "public: void
> > __thiscall v8::internal::Time::SetToCurrentTime(void)" (?
> > settocurrentt...@time@inter...@v8@@QAEXXZ)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__b...@12 referenced in function "public: virtual bool
> > __thiscall v8::internal::Win32Socket::Bind(int)" (?
> > b...@win32socket@inter...@v8@@uae...@z)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__ht...@4 referenced in function "public: virtual bool
> > __thiscall v8::internal::Win32Socket::Bind(int)" (?
> > b...@win32socket@inter...@v8@@uae...@z)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__ht...@4 referenced in function "public: virtual bool
> > __thiscall v8::internal::Win32Socket::Bind(int)" (?
> > b...@win32socket@inter...@v8@@uae...@z)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__lis...@8 referenced in function "public: virtual bool
> > __thiscall v8::internal::Win32Socket::Listen(int)const " (?
> > lis...@win32socket@inter...@v8@@ube...@z)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__acc...@12 referenced in function "public: virtual class
> > v8::internal::Socket * __thiscall
> > v8::internal::Win32Socket::Accept(void)const " (?
> > acc...@win32socket@inter...@v8@@ubepavsoc...@23@XZ)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__freeaddri...@4 referenced in function "public: virtual
> > bool __thiscall v8::internal::Win32Socket::Connect(char const *,char
> > const *)" (?conn...@win32socket@inter...@v8@@uae_np...@z)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__conn...@12 referenced in function "public: virtual bool
> > __thiscall v8::internal::Win32Socket::Connect(char const *,char const
> > *)" (?conn...@win32socket@inter...@v8@@uae_np...@z)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__getaddri...@16 referenced in function "public: virtual
> > bool __thiscall v8::internal::Win32Socket::Connect(char const *,char
> > const *)" (?conn...@win32socket@inter...@v8@@uae_np...@z)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__closesoc...@4 referenced in function "public: virtual
> > bool __thiscall v8::internal::Win32Socket::Shutdown(void)" (?
> > shutd...@win32socket@inter...@v8@@UAE_NXZ)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__shutd...@8 referenced in function "public: virtual bool
> > __thiscall v8::internal::Win32Socket::Shutdown(void)" (?
> > shutd...@win32socket@inter...@v8@@UAE_NXZ)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__s...@16 referenced in function "public: virtual int
> > __thiscall v8::internal::Win32Socket::Send(char const *,int)const " (?
> > s...@win32socket@inter...@v8@@ubehp...@z)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__r...@16 referenced in function "public: virtual int
> > __thiscall v8::internal::Win32Socket::Receive(char *,int)const " (?
> > rece...@win32socket@inter...@v8@@ubehp...@z)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__setsock...@20 referenced in function "public: virtual
> > bool __thiscall v8::internal::Win32Socket::SetReuseAddress(bool)" (?
> > setreuseaddr...@win32socket@inter...@v8@@uae_...@z)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__wsastar...@8 referenced in function "public: static bool
> > __cdecl v8::internal::Socket::Setup(void)" (?
> > se...@socket@inter...@v8@@SA_NXZ)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__wsagetlaster...@0 referenced in function "public: static
> > int __cdecl v8::internal::Socket::LastError(void)" (?
> > laster...@socket@inter...@v8@@SAHXZ)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__nt...@4 referenced in function "public: static unsigned
> > short __cdecl v8::internal::Socket::NToH(unsigned short)" (?
> > n...@socket@inter...@v8@@s...@z)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__nt...@4 referenced in function "public: static unsigned
> > int __cdecl v8::internal::Socket::NToH(unsigned int)" (?
> > n...@socket@inter...@v8@@s...@z)
> > 1>v8_g.lib(platform-win32.obj) : error LNK2019: unresolved external
> > symbol __imp__soc...@12 referenced in function "public: __thiscall
> > v8::internal::Win32Socket::Win32Socket(void)" (??
> > 0win32soc...@internal@v8@@q...@xz)
>
> > On Sep 1, 2:11 am, Corey <[email protected]> wrote:
> > > Yeah, I switched to the bleeding edge and found the AMD64/amd64
> > > problem fixed.
>
> > > Well, I tried the VC++ x86 setup batch a couple times already, with no
> > > luck, and I initially tried that shorter env parameter which didn't
> > > work at all (scons couldn't find the compiler then).
>
> > > Ah, compiling as a static library worked just fine, I don't know why I
> > > didn't try that, thank you!
>
> > > On Sep 1, 2:02 am, Søren Gjesse <[email protected]> wrote:
>
> > > > Hi,
>
> > > > The AMD64/amd64 think on Windows 7 should be fixed in
> > > > r5378<http://code.google.com/p/v8/source/detail?r=5378>
> > > > .
>
> > > > Regarding the linking problem I suggest that you use the "Visual Studio
> > 2010
> > > > Command Prompt" shortcut (assuming that Visual Studio 2010 has one) or
> > run
>
> > > > > :C:\Program Files
>
> > > > (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat x86
>
> > > > at a standard command prompt (assuming that Visual Studio 2010 still
> > > > supplies "vcvarsall.bat". Having done that you can shorten your compile
> > > > command
>
> > > > > scons mode=debug library=shared
>
> > > > env="PATH:%PATH%,LIB=%LIB%,INCLUDE=%INCLUDE%"
>
> > > > Have you tried a a static library or the x64 build (passing amd64
> > > > to vcvarsall.bat should set up the environment variables for a 64-bit).
>
> > > > Regards,
> > > > Søren
>
> > > > On Wed, Sep 1, 2010 at 07:52, Corey <[email protected]> wrote:
> > > > > Update:
> > > > > I've managed to get it to compile, but not link, using this command
> > > > > (thanks to help from the Wiki):
>
> > > > > scons mode=debug library=shared env="PATH:C:\Program Files
> > > > > (x86)\Microsoft Visual Studio 10.0\VC\bin;C:\Program Files
> > > > > (x86)\Microsoft Visual Studio 10.0\Common7\IDE;C:\Program Files
> > > > > (x86)\Microsoft Visual Studio 10.0\Common7\IDE;C:\Program Files
> > > > > (x86)\Microsoft Visual Studio 10.0\Common7\Tools,INCLUDE:C:\Program
> > > > > Files (x86)\Microsoft Visual Studio 10.0\VC\include;C:\Program Files
> > > > > (x86)\Microsoft SDKs\Windows\v7.0A\Include;C:\Program Files
> > > > > (x86)\Microsoft SDKs\Windows\v7.0A\Include,LIB;C:\Program Files
> > > > > (x86)\Microsoft Visual Studio 10.0\VC\lib;C:\Program Files
> > > > > (x86)\Microsoft SDKs\Windows\v7.0A\Lib;"
>
> > > > > The error I get when linking is this:
>
> > > > > LIBCMTD.lib(crt0dat.obj) : fatal error LNK1112: module machine type
> > > > > 'x64' conflicts with target machine type 'X86'
>
> > > > > I've check the environment paths many times to make sure they're set
> > > > > to the x86 versions, and I've made sure that the build script is
> > > > > attempting to build as 'ia32' but nothing seems to work.
>
> > > > > --
> > > > > v8-users mailing list
> > > > > [email protected]
> > > > >http://groups.google.com/group/v8-users
>
> > --
> > v8-users mailing list
> > [email protected]
> >http://groups.google.com/group/v8-users

-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users

Reply via email to