[MacPorts] #28066: nodejs: Headers from the c-ares port conflict with the bundled c-ares headers
MacPorts
noreply at macports.org
Mon Mar 7 23:11:04 PST 2011
#28066: nodejs: Headers from the c-ares port conflict with the bundled c-ares
headers
-----------------------------------------+----------------------------------
Reporter: david.easter@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: c-ares | Port: nodejs
-----------------------------------------+----------------------------------
Comment(by david.easter@…):
Yes. With c-ares at 1.7.0_0 installed:
{{{
/usr/bin/g++-4.0 [...] -I/opt/local/include [...] -Idefault/deps/c-ares
-I../deps/c-ares -Idefault/deps/c-ares/darwin-ia32 -I../deps/c-ares
/darwin-ia32
}}}
{{{
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_nodejs/work/node-v0.4.2$
sudo /usr/bin/make all
Waf: Entering directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_nodejs/work/node-v0.4.2/build'
DEST_OS: darwin
DEST_CPU: ia32
Parallel Jobs: 1
Product type: program
[61/74] cxx: src/node_cares.cc -> build/default/src/node_cares_4.o
/usr/bin/g++-4.0 -O2 -arch i386 -pthread -arch i386 -m32 -g -O3
-I/opt/local/include -I/opt/local/include -DHAVE_OPENSSL=1
-DEV_FORK_ENABLE=0 -DEV_EMBED_ENABLE=0 -DEV_MULTIPLICITY=0
-DX_STACKSIZE=65536 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-DEV_MULTIPLICITY=0 -DHAVE_FDATASYNC=0 -DPLATFORM="darwin" -D__POSIX__=1
-Wno-unused-parameter -D_FORTIFY_SOURCE=2 -DNDEBUG -Idefault/src -I../src
-Idefault/deps/libeio -I../deps/libeio -Idefault/deps/http_parser
-I../deps/http_parser -Idefault/deps/v8/include -I../deps/v8/include
-Idefault/deps/libev -I../deps/libev -Idefault/deps/c-ares
-I../deps/c-ares -Idefault/deps/c-ares/darwin-ia32 -I../deps/c-ares
/darwin-ia32 -I/opt/local/include -Ideps/v8/include ../src/node_cares.cc
-c -o default/src/node_cares_4.o
../src/node_cares.cc: In function ‘void
node::ParseAnswerMX(node::QueryArg*, unsigned char*, int)’:
../src/node_cares.cc:367: error: ‘ares_parse_mx_reply’ was not declared in
this scope
../src/node_cares.cc:376: error: invalid use of undefined type ‘struct
node::ares_mx_reply’
../src/node_cares.cc:365: error: forward declaration of ‘struct
node::ares_mx_reply’
../src/node_cares.cc:379: error: invalid use of undefined type ‘struct
node::ares_mx_reply’
../src/node_cares.cc:365: error: forward declaration of ‘struct
node::ares_mx_reply’
../src/node_cares.cc:380: error: invalid use of undefined type ‘struct
node::ares_mx_reply’
../src/node_cares.cc:365: error: forward declaration of ‘struct
node::ares_mx_reply’
Waf: Leaving directory
`/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_nodejs/work/node-v0.4.2/build'
Build failed: -> task failed (err #1):
{task: cxx node_cares.cc -> node_cares_4.o}
make: *** [program] Error 1
}}}
It works if c-ares at 1.7.4_0 is installed, but it's still finding the
includes at /opt/local/include (from the c-ares port) instead of the ones
bundled with nodejs.
--
Ticket URL: <https://trac.macports.org/ticket/28066#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list