I think you're close. I suggest you read the configure script that's in the
root of the node source tree, it'll help figure out the options.

I think all you need is --shared-v8-includes


On Sat, Apr 5, 2014 at 6:45 AM, Marco Dac <[email protected]> wrote:

> Thanks four your support, but i've to bother you with another question,
> i've recompiled v8ppc with the "library=shared" args and it's all fine.
> I've copied the contents of ppc.release in the /usr/lib/v8ppc folder,
> here is the content:
>
> dac@ibook:/usr/lib/v8ppc$ ls -l
> total 22992
> -rwxr-xr-x  1 root root 17979178 Apr  5 11:47 cctest
> -rwxr-xr-x  1 root root    52202 Apr  5 11:47 d8
> drwxr-xr-x  2 root root     4096 Apr  5 11:47 lib.target
> -rwxr-xr-x  1 root root    19690 Apr  5 11:47 lineprocessor
> -rwxr-xr-x  1 root root  5189321 Apr  5 11:47 mksnapshot
> drwxr-xr-x  3 root root     4096 Apr  5 11:47 obj
> drwxr-xr-x 17 root root     4096 Apr  5 11:47 obj.target
> -rwxr-xr-x  1 root root   226143 Apr  5 11:47 preparser
> -rwxr-xr-x  1 root root    36560 Apr  5 11:47 process
> -rwxr-xr-x  1 root root    19273 Apr  5 11:47 shell
>
> (Since i was not sure about what i really needed i copied it all...)
> I've also configured the LD_LIBRARY_PATH in my .profile
>
> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/v8ppc/lib.target/libv8.so
>
> Now I've cloned the node git repo and I'm trying to build it following the
> Andrew Low suggestion, I've done:
>
> sudo ./configure --shared-v8
> --shared-v8-libpath=/usr/lib/v8ppc/lib.target/libv8.so
>
> This is the ./configure output
> dac@ibook:~/Labs/nodejsLibrary/node$ sudo ./configure --shared-v8
> --shared-v8-libpath=/usr/lib/v8ppc/lib.target/libv8.so
> { 'target_defaults': { 'cflags': [],
>                        'default_configuration': 'Release',
>                        'defines': [],
>                        'include_dirs': [],
>                        'libraries': [
> '-L/usr/lib/v8ppc/lib.target/libv8.so',
>                                       '-lv8']},
>   'variables': { 'clang': 0,
>                  'gcc_version': 46,
>                  'host_arch': 'ppc',
>                  'node_byteorder': 'big',
>                  'node_install_npm': 'true',
>                  'node_prefix': '',
>                  'node_shared_cares': 'false',
>                  'node_shared_http_parser': 'false',
>                  'node_shared_libuv': 'false',
>                  'node_shared_openssl': 'false',
>                  'node_shared_v8': 'true',
>                  'node_shared_zlib': 'false',
>                  'node_tag': '',
>                  'node_unsafe_optimizations': 0,
>                  'node_use_dtrace': 'false',
>                  'node_use_etw': 'false',
>                  'node_use_openssl': 'true',
>                  'node_use_perfctr': 'false',
>                  'node_use_systemtap': 'false',
>                  'python': '/usr/bin/python',
>                  'target_arch': 'ppc',
>                  'v8_enable_gdbjit': 0,
>                  'v8_no_strict_aliasing': 1,
>                  'v8_use_snapshot': 'true'}}
> creating  ./config.gypi
> creating  ./config.mk
>
> And then:
> sudo make
>
> But here is the a problem, seems like the compiler doesn't found the v8.h
> file:
>
> /Labs/nodejsLibrary/node/out/Release/obj.target/node/src/fs_event_wrap.o
> ../src/fs_event_wrap.cc
> In file included from ../src/fs_event_wrap.cc:22:0:
> ../src/node.h:62:16: fatal error: v8.h: No such file or directory
> compilation terminated.
> make[1]: ***
> [/home/dac/Labs/nodejsLibrary/node/out/Release/obj.target/node/src/fs_event_wrap.o]
> Error 1
> make[1]: Leaving directory `/home/dac/Labs/nodejsLibrary/node/out'
> make: *** [node] Error 2
>
> There is something else I'm missing? I've to put also the source
> code together with the library folder?
>
>
>
>
> On Friday, April 4, 2014 9:15:09 PM UTC+2, Andrew Low wrote:
>
>> Cool - thanks *Jérémy Lal*. The Ubuntu builds have the PowerPC code
>> merged in here: https://launchpad.net/ubuntu/trusty/+source/libv8-3.
>> 14/3.14.5.8-5ubuntu2
>>
>> As you probably know - I've got a libv8 branch here: https://github.com/
>> andrewlow/v8ppc/tree/libv8-3.14
>>
>> However, *Marco Dac* is building on a G4 based chip - this is not yet
>> supported in our main code streams. He'll need to look at the slightly
>> behind https://github.com/andrewlow/v8ppc/tree/g4compat branch.
>>
>> Also, it sounds like Marco is trying to build Node.js with V8 statically
>> linked in. There is a little bit of magic here most of which you'll find in
>> this patch done by the node folks https://github.com/
>> andrewlow/node/commit/e2385839d7bde937334e34da082293cae877fe2f
>>
>> If you look through the git log you'll find the v8 patches applied etc,
>> as Node will backport some changes into the older stream they have in deps.
>>
>> The easier way to get running is to build v8 as a shared library pass
>> "library=shared" along on the make command line.
>>
>> Then for Node - you need to pass --shared-v8 into ./configure and
>> probably also --shared-v8-libpath to point to where it is.  You may need to
>> also set LD_LIBRARY_PATH depending on where the libv8 is installed.
>>
>>
>>
>> On Thu, Apr 3, 2014 at 4:47 PM, Jérémy Lal <[email protected]> wrote:
>>
>>> Le jeudi 03 avril 2014 à 13:44 -0700, Marco Dac a écrit :
>>> > Hi, after finding out about this porting, I wanted to give it a try,
>>> but
>>> > now I'm stuck, here is what i've done until now.
>>> > I've an iBook G4 with Debian.
>>>
>>> Hold your breath ! libv8-3.14 ppc patches are coming to debian/sid soon.
>>>
>>> Jérémy.
>>>
>>>
>>> --
>>> --
>>> Job Board: http://jobs.nodejs.org/
>>> Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-
>>> Posting-Guidelines
>>> You received this message because you are subscribed to the Google
>>> Groups "nodejs" group.
>>> To post to this group, send email to [email protected]
>>>
>>> To unsubscribe from this group, send email to
>>> [email protected]
>>>
>>> For more options, visit this group at
>>> http://groups.google.com/group/nodejs?hl=en?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "nodejs" group.
>>> To unsubscribe from this topic, visit https://groups.google.com/d/
>>> topic/nodejs/ivGMr-C_m1Y/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> [email protected].
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "nodejs" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/nodejs/ivGMr-C_m1Y/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to