[MacPorts] #56706: doxygen @1.8.13 fails to build when arpack is installed

[MacPorts]

#56706: doxygen @1.8.13 fails to build when arpack is installed
---------------------------+----------------------
  Reporter:  ShadSterling  |      Owner:  cssdev
      Type:  defect        |     Status:  assigned
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.5.2
Resolution:                |   Keywords:
      Port:  doxygen       |
---------------------------+----------------------
Changes (by ryandesign):

 * cc: isoboroff (added)


Comment:

 Replying to [comment:5 isoboroff]:
 > I also have a problem building this port.  Here is the bit that fails
 (definition.cpp, problems finding md5 stuff) in main.log...
 >
 > {{{
 > :info:build cd
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.13/src
 && /usr/bin/clang++  -DYY_BUF_SIZE=262144 -DYY_READ_BUF_SIZE=262144
 -I/opt/local/include
 -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.13/qtools
 -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.13/libmd5
 -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.13/vhdlparser
 -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.13/src
 -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.13/generated_src
 -pipe -Os -stdlib=libc++ -DNDEBUG -arch x86_64 -mmacosx-version-min=10.13
 -o CMakeFiles/_doxygen.dir/definition.cpp.o -c
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_doxygen/doxygen/work/doxygen-1.8.13/src/definition.cpp
 > :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.13/src/dirdef.cpp:92:3:
 error: use of undeclared identifier 'MD5Buffer'
 > :info:build   MD5Buffer((const unsigned char
 *)anchor.data(),anchor.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.13/src/dirdef.cpp:93:3:
 error: use of undeclared identifier 'MD5SigToString'
 > :info:build   MD5SigToString(md5_sig,sigStr.rawData(),33);
 > :info:build   ^
 > :info:build 2 errors generated.
 > }}}

 This is a similar problem. It has the same underlying cause—`-I` flags in
 the wrong order—except that in this case the port that installed the
 conflicting file is not arpack but libmd. This was also reported
 separately in #59037.

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

 Chris, can you fix the build system to put the `-I` flags in the right
 order? If that's not possible right now, could you at least use the
 conflicts_build portgroup?

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