[MacPorts] #28066: nodejs: Headers from the c-ares port conflict with the bundled c-ares headers

MacPorts noreply at macports.org
Wed Nov 23 07:22:16 PST 2011


#28066: nodejs: Headers from the c-ares port conflict with the bundled c-ares
headers
------------------------------------------+---------------------------------
  Reporter:  david.easter@…               |       Owner:  ciserlohn@…           
      Type:  defect                       |      Status:  closed                
  Priority:  Normal                       |   Milestone:                        
 Component:  ports                        |     Version:  1.9.2                 
Resolution:  fixed                        |    Keywords:  c-ares                
      Port:  nodejs                       |  
------------------------------------------+---------------------------------

Comment(by ciserlohn@…):

 Replying to [comment:8 jmr@…]:
 > Fixed, r87475. Upstream really needs to make sure their internal include
 paths come first; has this been reported to them?

 {{{
 +# build system doesn't ensure its internal include paths come first
 (#28066)
 +configure.cppflags      -isystem ${prefix}/include
 }}}

 The change did not fixed the problem. As you can see in the build.arg-
 append section in the portfile the configure.cppflags are not used. And
 even if the configure.cppflags were used the macports headers would be
 found first as the '-isystem' directories are searched after '-I'
 directories.

 Actually this was not a problem before your change because the
 configure.cppflags were not used. The same applies for #28562 and #29927.
 However, removing the warning and installation prevention should have been
 done earlier as well as closing the tickets.

-- 
Ticket URL: <https://trac.macports.org/ticket/28066#comment:9>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list