psutil library for node

[christkv]

I'm slowly working on rewriting the python lib psutil for node but I'm running into a problem on linux. It builds perfectly with clang++ but fails to link correctly with g++. The code is here

https://github.com/christkv/node-psutil

I would really really appreciate it if anyone could shed some light on the problem as I've pretty much wasted a couple of days trying to figure out and I'm sure it's something stupid I've forgot to add in the gyp file.

I published it under psutil on npm so just grab latest if you want to try it out. It's a bit barebones right now and only supports linux and darwin but I'll keep adding to it over time to have a proper full port in due time.

[Paddy Byers]

Hi,

I would really really appreciate it if anyone could shed some light on the problem as I've pretty much wasted a couple of days trying to figure out and I'm sure it's something stupid I've forgot to add in the gyp file.

If you disambiguate all references to Handle as v8::Handle then it builds for me, on Debian and Darwin. I guess there is a conflict with a definition in one of the various things you're including.

See https://github.com/paddybyers/node-psutil/commit/7e77d53e295e830334aaaad862edbac3f93dca76

Paddy 

[mscdex]

On Sep 6, 5:20 pm, Paddy Byers <paddy.by...@gmail.com> wrote:
> If you disambiguate all references to Handle as v8::Handle then it builds
> for me, on Debian and Darwin. I guess there is a conflict with a definition
> in one of the various things you're including.

Line 39 probably does not help any:

// using namespace v8;

[christkv]

ok cool I'll go through all the stuff with a comb. wonder why g++ is so picky while clang++ is not.

[Oleg Efimov (Sannis)]

I do not know why clang is so lenient ;) but it look like a bad idea to place all code in header files and trying to link them together.

I will try to build this on linux on the weekend.

Also, why are you place "static" declaration into binding.gyp? *.node files are dynamic libraries.

пятница, 7 сентября 2012 г., 11:15:46 UTC+4 пользователь christkv написал:

[Oleg Efimov (Sannis)]

There are many resources in www, but this is a good one: http://lists.gnu.org/archive/html/openexr-devel/2003-10/msg00035.html

Maybe clang linker is a bit entelligent, but previously I think that it use standard ld.

пятница, 7 сентября 2012 г., 11:15:46 UTC+4 пользователь christkv написал:

ok cool I'll go through all the stuff with a comb. wonder why g++ is so picky while clang++ is not.

[christkv]

Hi Oleg any help would be appreciated as none of the suggestions currently seems to work. It build correctly but if you run the a test using the lib you get.

parallels@parallels-Parallels-Virtual-Platform:~/coding/checkouts/node-psutil$ nodeunit test/networkstat_test.js 

module.js:485

  process.dlopen(filename, module.exports);

          ^

Error: /home/parallels/coding/checkouts/node-psutil/build/Release/psutil_lib_osx.node: undefined symbol: _ZTV6Worker

    at Object.Module._extensions..node (module.js:485:11)

    at Module.load (module.js:356:32)

    at Function.Module._load (module.js:312:12)

    at Module.require (module.js:362:17)

    at require (module.js:378:17)

    at Object.<anonymous> (/home/parallels/coding/checkouts/node-psutil/lib/psutil.js:1:79)

    at Module._compile (module.js:449:26)

    at Object.Module._extensions..js (module.js:467:10)

    at Module.load (module.js:356:32)

    at Function.Module._load (module.js:312:12)

Meaning the g++ linker is doing something differently. Also if I do nm on the .node library that reference shows up as undefined. 

[Marcel Laverdet]

Never never never never never never never put "using namespace" in a header file. Or before *any* #include.

--
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 nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[christkv]

That does not help either. I've put a single "worker" version here

https://github.com/christkv/node-psutil/tree/no_using_namespace

and it builds with g++ but does fails when running the virtual_memory_test as indicated above.

[Oleg Efimov (Sannis)]

I think the best way will be to keep original psutils files layout. It is more common to use different files for different platforms, that write hundred-lines #ifdefs.

If there was a set of *.cc + *.h files, it should be linked well.

пятница, 7 сентября 2012 г., 11:55:57 UTC+4 пользователь christkv написал:

[christkv]

well finally fixed it had to do the separation of concerns. G++ truly
is the Yoda of C++ compilers.

[Oleg Efimov (Sannis)]

Nice!

суббота, 8 сентября 2012 г., 13:53:54 UTC+4 пользователь christkv написал: