Hi group-
Finally, after 2 days of consecutive tracing and debugging, I had this 
sorted. However, I am not sure if this is due to my customized installation 
of Python. I updated the code below in 
~node_modules/node-gyp/lib/configure.js (changed original as in commented 
line 93 to 94:

93     // var env = { TERM: 'dumb', PATH: process.env.PATH};
94     var env = process.env

I will truly appreciate if any node.js experts in the group can help with a 
rational with the above change?

Thanks again
Feng

On Tuesday, September 17, 2013 5:17:08 PM UTC-4, [email protected] wrote:
>
> Thanks Jose. 
>
> But I built the python from source and had a customized installation. 
> And libpython2.7.so.1.0 is presented in the following:$PYTHONPATH as well 
> as $LD_LIBRARY_PATH. Does node or node-gyp search a rather different 
> environment virable for shared libraries?
>
> I also specifed the binding.gyp as below, but it seems still not picking 
> up.
>
> {
>     'targets': [
>         {
>             'target_name': 'hello',
>             'sources': [ 'src/hello.cc' ],
>             'include_dirs': ['/path/to/my/include'],
>             'link_settings': {
>                 'library_dirs': [
>                     '/path/to/my/libpython2.7.so.1.0'
>                 ]
>             }
>         }
>     ]
> }
>  
>
> Feng
>
>
> On Tuesday, September 17, 2013 4:40:48 PM UTC-4, Jose Luis Rivas wrote:
>>
>> On 09/17/2013 12:51 PM, [email protected] wrote: 
>> > ~/examples/node.js/my_node_addon-1[13:14]% node-gyp configure 
>> > gyp info it worked if it ends with ok 
>> > gyp info using node-gyp\@0.10.10 
>> > gyp info using node\@0.10.18 | linux | x64 
>> > gyp ERR! configure error 
>> > gyp ERR! stack Error: Command failed: python: error while loading 
>> shared 
>> > libraries: *libpython2.7.so.1.0*: cannot open shared object file: No 
>> > such file or directory 
>>
>> > 
>> > *But when I run python alone it loads the shared lib just fine:* 
>> > ~/examples/node.js/my_node_addon-1[13:14]% python -V 
>> > Python 2.7.3 
>>
>> No, the shared libraries come in a python-dev package, not the regular 
>> executables. 
>>
>> Search the development libraries for python, install them and you will 
>> not have this issue anymore. 
>>
>>
>> -- 
>> Jose Luis Rivas 
>> http://joseluisrivas.net/ 
>>
>

-- 
-- 
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/groups/opt_out.

Reply via email to