[
https://issues.apache.org/jira/browse/THRIFT-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14300024#comment-14300024
]
Andrew de Andrade commented on THRIFT-2959:
-------------------------------------------
Another possible explanation is the the makefile execution of npm install uses
the `--no-bin-links` arg (but I can't think of any reason why that flag would
be set except in conjunction with the --global/-g flag (i.e. I can see why
someone, for security or naming conflict reasons with another binary, might
want a library available globally, but not want that library to put an
executable accessible via $PATH.)
automake and autoconf are pretty new to me, so I'll see how far I can get in my
sleuthing. Truth is that I found the entire `make check` experience wholly
overwhelming since there is so much noise on stdout even for passing tests.
(generally I only want to see additional info when things fail or when I set
logging levels high).
> nodejs: fix binary unit tests
> -----------------------------
>
> Key: THRIFT-2959
> URL: https://issues.apache.org/jira/browse/THRIFT-2959
> Project: Thrift
> Issue Type: Bug
> Components: Node.js - Library
> Environment: Trusty64 Vagrant Box
> Reporter: Andrew de Andrade
> Priority: Minor
> Attachments: thrift-2959-nodejs-fix-binary-unit-tests.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
