[MacPorts] #59037: doxygen @1.8.15 fails to build when libmd is installed (was: doxygen upgrade fails to build doxygen @1.8.14_0+docs ---> doxygen @1.8.15_0+docs)

MacPorts noreply at macports.org
Sat Oct 12 21:34:05 UTC 2019


#59037: doxygen @1.8.15 fails to build when libmd is installed
------------------------------+----------------------
  Reporter:  TheLastLovemark  |      Owner:  cssdev
      Type:  defect           |     Status:  assigned
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.5.4
Resolution:                   |   Keywords:
      Port:  doxygen          |
------------------------------+----------------------

Comment (by ryandesign):

 The log says:

 {{{
 :info:build
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.15/src/definition.cpp:555:3:
 error: use of undeclared identifier 'MD5Buffer'
 :info:build   MD5Buffer((const unsigned char
 *)docStr.data(),docStr.length(),md5_sig);
 :info:build   ^
 :info:build
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.15/src/definition.cpp:556:3:
 error: use of undeclared identifier 'MD5SigToString'
 :info:build   MD5SigToString(md5_sig,sigStr.rawData(),33);
 :info:build   ^
 :info:build 2 errors generated.
 }}}

 This was also reported in comment:ticket:56706:5, and I see it too with
 1.8.16, if I have libmd installed, which provides
 /opt/local/include/md5.h. It's a similar problem to the one reported in
 #56706: doxygen puts its `-I` flags in the wrong order, so the
 `-I/opt/local/include` that MacPorts adds appears before the project's own
 include directories, rather than after, and therefore files installed in
 /opt/local/include shadow those that the port actually wants to use.

 To work around the problem, temporarily deactivate the port that provides
 the conflicting file (libmd in this case), then build doxygen, then you
 can reactivate the conflicting port.

-- 
Ticket URL: <https://trac.macports.org/ticket/59037#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list