[MacPorts] #48231: doxygen @1.8.9.1: update to 1.8.10

MacPorts noreply at macports.org
Thu Jul 2 23:51:26 PDT 2015


#48231: doxygen @1.8.9.1: update to 1.8.10
-----------------------------+----------------------
  Reporter:  mschamschula@…  |      Owner:  css@…
      Type:  update          |     Status:  new
  Priority:  Normal          |  Milestone:
 Component:  ports           |    Version:  2.3.3
Resolution:                  |   Keywords:  haspatch
      Port:  doxygen         |
-----------------------------+----------------------
Changes (by ryandesign@…):

 * cc: css@… (removed)
 * cc: ryandesign@… (added)
 * owner:  macports-tickets@… => css@…


Comment:

 There are numerous issues to be resolved here before this could be
 committed, but a big one is the libiconv patch you attached to prevent the
 use of MacPorts libiconv. That won't work, because the patch includes
 details specific to your MacPorts installation, including the MacPorts
 prefix, the location of Xcode, the build architecture, the C++ std
 library, the deployment target, the location of your ports tree, maybe
 more.

 We want to build with MacPorts libiconv. The missing symbols error you saw
 when building with MacPorts libiconv should be reported to the developers
 of doxygen so they can fix it.

 The missing symbols error often indicates that the headers of MacPorts
 libiconv are being used while the library of OS X libiconv is being used,
 or vice versa.

 Looks like there are cmake variables that one should be able to set to
 tell the build system which libiconv to use (`ICONV_INCLUDE_DIR:PATH` and
 `ICONV_LIBRARY:FILEPATH`) but setting these has no effect. I suspect this
 is another symptom of the same problem.

-- 
Ticket URL: <https://trac.macports.org/ticket/48231#comment:1>
MacPorts <https://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list