Sitelet https://github.com/nodejs/node/issues/4895
Skip to content

Install and shared library issues for nodejs V5.5.0 on Solaris 10 x86 #4895

Description

@ApolonTorq

An unxz and untar of node-v5.5.0-sunos-x64.tar.xz results in:

x node-v5.5.0-sunos-x64/lib/node_modules/npm/node_modules/which/node_modules/is-absolute/node_modules, 0 bytes, 0 tape blocks
tar: ././@LongLink: typeflag 'L' not recognized, converting to regular file
x ././@LongLink, 113 bytes, 1 tape blocks
x node-v5.5.0-sunos-x64/lib/node_modules/npm/node_modules/which/node_modules/is-absolute/node_modules, 0 bytes, 0 tape blocks
tar: ././@LongLink: typeflag 'L' not recognized, converting to regular file
x ././@LongLink, 125 bytes, 1 tape blocks
x node-v5.5.0-sunos-x64/lib/node_modules/npm/node_modules/which/node_modules/is-absolute/node_modules, 0 bytes, 0 tape blocks
tar: directory checksum error

An ldd on the resulting node executable shows the following shared library resolution issues:

        libkstat.so.1 =>         /lib/64/libkstat.so.1
        libumem.so.1 =>  /lib/64/libumem.so.1
        libsocket.so.1 =>        /lib/64/libsocket.so.1
        libsocket.so.1 (SUNW_1.7) =>     (version not found)
        libnsl.so.1 =>   /lib/64/libnsl.so.1
        librt.so.1 =>    /lib/64/librt.so.1
        libsendfile.so.1 =>      /lib/64/libsendfile.so.1
        libstdc++.so.6 =>        (file not found)
        libm.so.2 =>     /lib/64/libm.so.2
        libgcc_s.so.1 =>         (file not found)
        libpthread.so.1 =>       /lib/64/libpthread.so.1
        libc.so.1 =>     /lib/64/libc.so.1
        libc.so.1 (ILLUMOS_0.17) =>      (version not found)
        libc.so.1 (ILLUMOS_0.5) =>       (version not found)
        libmp.so.2 =>    /lib/64/libmp.so.2
        libmd.so.1 =>    /lib/64/libmd.so.1
        libscf.so.1 =>   /lib/64/libscf.so.1
        libaio.so.1 =>   /lib/64/libaio.so.1
        libdoor.so.1 =>  /lib/64/libdoor.so.1
        libuutil.so.1 =>         /lib/64/libuutil.so.1
        libgen.so.1 =>   /lib/64/libgen.so.1

This issue is not a high priority for me as we'll probably go with a later Solaris version or Open Indiana. This issue was submitted based on a request by @misterdjules.

Activity

  1. added
    smartosIssues and PRs related to the SmartOS platform.
    on Jan 27, 2016
  2. misterdjules commented on Jan 27, 2016

    @misterdjules

    Thank you for filing that issue. This problem is due to the fact that sunos binaries are built on a SmartOS machine. You can find more details in a gist I wrote. My recommendation would be, in order of preference, to:

    1. let package managers handle distribution of Node.js binaries on Solaris
    2. help the @nodejs/build team setup a Solaris build environment to publish solaris binaries

    There's been a few new issues created lately about not being able to run sunos node binaries on various Solaris derivatives. @nodejs/build Would it help to create a reference issue in @nodejs/build that summarizes the situation and link to all the existing related issues in nodejs/node?

  3. misterdjules commented on Jan 27, 2016

    @misterdjules

    Closing this issue as a duplicate of #3349, but the information in this issue is still very useful, so thank you very much for taking the time to file it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    smartosIssues and PRs related to the SmartOS platform.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions