Closed GoogleCodeExporter closed 9 years ago
I'm build v8cgi on my MacOSX. All I need SConstruct.patch and v8cgi.conf.darwin
(attached). After build put 'lib' to '/usr/local/lib/v8cgi' and 'v8cgi' to
'/usr/local/bin'.
Original comment by mr.ve...@gmail.com
on 30 Aug 2009 at 11:51
Attachments:
this patches already merge to trunk, maybe close issue?
Original comment by mr.ve...@gmail.com
on 8 Nov 2009 at 4:55
I was thinking about distributing binaries, like the zip for win32.
It's easier for newcomers...
But the compilation is easier now, so it's not a high priority.
Original comment by eric.abo...@gmail.com
on 8 Nov 2009 at 6:19
easier? =) now (r663) i cant build on macosx --
http://code.google.com/p/v8cgi/issues/detail?id=37
Original comment by mr.ve...@gmail.com
on 8 Nov 2009 at 6:52
that's definitly why binaries are useful :)
Original comment by eric.abo...@gmail.com
on 8 Nov 2009 at 6:55
Eric,
so you are able to compile v8cgi on MacOSX now? Can you please integrate your
solution into a SConstruct file and commit it? It would be really cool to have
v8cgi
build on Mac straight from the svn...
Original comment by ondrej.zara
on 8 Nov 2009 at 7:12
v8cgi now builds on Mac OSX with latest v8 :)
Original comment by ondrej.zara
on 7 Jan 2010 at 12:28
Ondrej, can you comment on whether this still seems to work and/or if there are
more complete instructions on how to install on osx. When I follow things with
clean
checkouts from today, I end up with this error:
g++ -o src/lib/binary/bytestring.os -c -Wall -O3 -fPIC -DHAVE_MMAN_H -
DHAVE_SLEEP -DCONFIG_PATH=/etc/v8cgi.conf -DVERSION=0.7.6dev -Ddarwin -
DDSO_EXT=dylib -Isrc -I/Users/moskov/sandbox/v8-src/v8/include
src/lib/binary/bytestring.cc
src/lib/binary/bytestring.cc: In function 'void
ByteString_init(v8::Handle<v8::FunctionTemplate>)':
src/lib/binary/bytestring.cc:112: error: invalid conversion from
'v8::Handle<v8::Value> (*)(size_t, const v8::AccessorInfo&)' to
'v8::Handle<v8::Value> (*)(uint32_t, const v8::AccessorInfo&)'
src/lib/binary/bytestring.cc:112: error: initializing argument 1 of 'void
v8::ObjectTemplate::SetIndexedPropertyHandler(v8::Handle<v8::Value>
(*)(uint32_t,
const v8::AccessorInfo&), v8::Handle<v8::Value> (*)(uint32_t,
v8::Local<v8::Value>,
const v8::AccessorInfo&), v8::Handle<v8::Boolean> (*)(uint32_t, const
v8::AccessorInfo&), v8::Handle<v8::Boolean> (*)(uint32_t, const
v8::AccessorInfo&),
v8::Handle<v8::Array> (*)(const v8::AccessorInfo&), v8::Handle<v8::Value>)'
If I resolve that by changing the function definition in bytestring.cc to:
v8::Handle<v8::Value> _get(uint32_t index, const v8::AccessorInfo &info) {
and make similar changes in bytearray.cc (for _get and _set), I can get past
the error
but am left with:
Undefined symbols:
"_iconv_close", referenced from:
ByteStorage::transcode(char const*, char const*)in bytestorage.os
ByteStorage::transcode(char const*, char const*)in bytestorage.os
ByteStorage::transcode(char const*, char const*)in bytestorage.os
ByteStorage::transcode(char const*, char const*)in bytestorage.os
"_iconv", referenced from:
ByteStorage::transcode(char const*, char const*)in bytestorage.os
"_iconv_open", referenced from:
ByteStorage::transcode(char const*, char const*)in bytestorage.os
ld: symbol(s) not found
collect2: ld returned 1 exit status
scons: *** [lib/binary.dylib] Error 1
scons: building terminated because of errors.
So I'm worried I'm following a rabbit hole here and there may be something
wrong at
a higher level. I also noticed that mr.veged never submitted the diff he linked
to in
comment 4 (that would have changed v8cgi SConstruct file to specify 32-bit).
Was
there some other resolution to the problem?
Original comment by dustin.m...@gmail.com
on 2 Feb 2010 at 2:27
Dustin,
the issues you are experiencing are caused by the recent Binary/B
implementation.
This code is still pretty new and was not yet tested on Mac OS X.
You resolved the issue with signature of "_get" in the best possible way. New
errors
with iconv are probably caused by the absence of explicit iconv linking; I will
look
into that soon.
The ultimate goal is to have v8cgi build on Mac OS X without any hacks. For
now, you
might try to comment out the part of SConstruct file which handles the binary
module
compilation.
Original comment by ondrej.zara
on 2 Feb 2010 at 5:08
Dustin,
please try updating to latest revision 762. I fixed some stuff regarding Mac
compilation there.
Original comment by ondrej.zara
on 2 Feb 2010 at 5:45
thanks, it is building successfully now
Original comment by dustin.m...@gmail.com
on 3 Feb 2010 at 7:18
v8cgi now relatively normally compiles on MacOSX - marking this issue as
obsolete.
Original comment by ondrej.zara
on 24 Jan 2011 at 10:51
Original issue reported on code.google.com by
eric.abo...@gmail.com
on 12 Aug 2009 at 9:38