Opened 3 years ago

Last modified 6 months ago

#68534 assigned defect

doxygen @1.9.8: fatal error: 'fmt/core.h' file not found

Reported by: kwolcott Owned by: mascguy (Christopher Nielsen)
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: Cc: michaellass (Michael Lass), Dave-Allured (Dave Allured), amadeus24, cooljeanius (Eric Gallager)
Port: doxygen

Description (last modified by ryandesign (Ryan Carsten Schmidt))

doxygen update build from source fails:

fmt/core.h' file not found
make[2]: *** [src/CMakeFiles/doxymain.dir/__/generated_src/commentscan.cpp.o] Error 1

arm64

Sonoma 14.0

Attachments (1)

doxygen_port_update_build_from_source_failed.log.bz2 (8.6 KB) - added by kwolcott 3 years ago.

Download all attachments as: .zip

Change History (12)

comment:1 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)
Summary: doxygen update build from source fails: fmt/core.h' file not founddoxygen @1.9.8: fatal error: 'fmt/core.h' file not found
Version: 2.8.1

The log says:

:info:build /opt/local/include/spdlog/fmt/fmt.h:31:14: fatal error: 'fmt/core.h' file not found
:info:build #    include <fmt/core.h>
:info:build              ^~~~~~~~~~~~

The doxygen port doesn't declare a dependency on the spdlog port and we have successful builds of doxygen on all buildbot workers that have tried to build this port (there isn't a Sonoma arm64 buildbot worker yet) so this may be an opportunistic use of spdlog. In fact it looks like doxygen includes a bundled copy of spdlog and is trying to use that but is inadvertently finding your MacPorts copy with which it is evidently not compatible.

If trace mode worked on Sonoma you could use that to hide spdlog during the doxygen build. But since it doesn't, you could deactivate spdlog for the duration of the doxygen build:

sudo port clean doxygen
sudo port -f deactivate spdlog
sudo port upgrade doxygen
sudo port activate spdlog

comment:2 Changed 3 years ago by kwolcott

Looks like the suggested workaround was successful. I'm quite impressed at the quality and response time of analysis of the problem and the resultant temporary fix.

comment:3 Changed 3 years ago by mascguy (Christopher Nielsen)

Owner: set to mascguy
Status: newassigned

I'll tackle this one

comment:4 Changed 3 years ago by barracuda156

Another doxygen 1.9.8 and spdlog issue is #68581

Thanks Ryan for pointing to this.

comment:5 Changed 3 years ago by michaellass (Michael Lass)

Cc: michaellass added

comment:6 Changed 19 months ago by mouse07410 (Mouse)

Also, a doxygen 1.11.0 and spdlog issue.

comment:7 Changed 14 months ago by Dave-Allured (Dave Allured)

Cc: Dave-Allured added

comment:8 Changed 10 months ago by ryandesign (Ryan Carsten Schmidt)

Cc: amadeus24 added

Has duplicate #73010.

comment:9 Changed 6 months ago by cooljeanius (Eric Gallager)

Cc: cooljeanius added

comment:10 Changed 6 months ago by cooljeanius (Eric Gallager)

Note that spdlog is a dependency of tiledb, which may be installed due to gdal's +tiledb variant. Also, the conflicts_build PortGroup could be used here, although, as mentioned in #59037 about doxygen's existing usage of conflicts_build (against libmd), that's not a permanent solution...

comment:11 Changed 6 months ago by kwolcott

I've successfully installed the doxygen port quite some time ago.

I think that this ticket can be closed.

Thanks, Ken Wolcott

Note: See TracTickets for help on using tickets.