Re: [nodejs] Any way of determining what ./configure options were used for a particular node binary?

[Ben Noordhuis]

On Mon, Oct 29, 2012 at 7:21 PM, Mike <mike.h...@gmail.com> wrote:
> Given a node binary, any easy way of determining what options were passed to
> ./configure when the binary was built?

Yes, for certain values of 'easy'.

$ node -pe process.config
{ target_defaults:
{ cflags: [],
default_configuration: 'Release',
defines: [],
include_dirs: [],
libraries: [] },
variables:
{ clang: 0,
gcc_version: 46,
host_arch: 'x64',
node_install_npm: true,
node_install_waf: true,
node_prefix: '/home/bnoordhuis/opt/node',
node_shared_openssl: false,
node_shared_v8: false,
node_shared_zlib: false,
node_unsafe_optimizations: 0,
node_use_dtrace: false,
node_use_etw: false,
node_use_openssl: true,
target_arch: 'x64',
v8_no_strict_aliasing: 1,
v8_use_snapshot: true } }

[Nathan Rajlich]

If you mean "5mb larger than the one in the Raspbian repository" then
I'd guess it's cause they're linking to a shared OpenSSL and zlib
(maybe even V8), whereas when you compile it manually those get
statically linked to the node binary (resulting in a larger size due
to the additional symbols).

> --
> 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

[Mike]

Easy enough, many thanks!

(note to self, process.config is only available for v0.7.7 and higher)

[Mike]

Correct... 

I took a closer look at the binaries -- besides libssl, libz, & libv8, the node in the Raspbian repository also linked to the shared ld-linux-armhf, libcares, libcrypto, libev, libutil libraries.