Pages of warnings appear during npm install #16

Closed
ARAtlas opened this Issue Mar 26, 2013 · 1 comment

Comments

Projects
None yet
2 participants

ARAtlas commented Mar 26, 2013

"Inbox" fills the npm install output with pages and pages of warnings. Is there any way to quiet those down? Here's an example extract:

lib/aliases.gperf:777:27: note: 'aliases' declared here
static const struct alias aliases[] =
^
../deps/libiconv/lib/iconv.c:188:22: warning: static variable 'stringpool2_contents' is used in an inline function with external
linkage [-Wstatic-in-inline]
if (!strcmp(str, stringpool2 + ptr->name))
^
../deps/libiconv/lib/iconv.c:173:38: note: expanded from macro 'stringpool2'

define stringpool2 ((const char *) &stringpool2_contents)

                                 ^

../deps/libiconv/lib/iconv.c:180:1: note: use 'static' to give inline function 'aliases2_lookup' internal linkage
__inline
^
static
../deps/libiconv/lib/iconv.c:168:35: note: 'stringpool2_contents' declared here
static const struct stringpool2_t stringpool2_contents = {
^
In file included from ../deps/libiconv/lib/iconv.c:238:
../deps/libiconv/lib/iconv_open2.h:84:32: warning: unused variable 'wcd' [-Wunused-variable]
struct wchar_conv_struct * wcd = (struct wchar_conv_struct *) cd;
^
In file included from ../deps/libiconv/lib/iconv.c:294:

Contributor

andris9 commented Jul 16, 2013

This is node-iconv issue, can't do anything about it.

@andris9 andris9 closed this Jul 16, 2013

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