Bug 247427 - graphics/openjpeg15 openjpeg.h header conflicts with the same header from graphics/openjpeg
Summary: graphics/openjpeg15 openjpeg.h header conflicts with the same header from gra...
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Dima Panov
Depends on:
Reported: 2020-06-19 17:40 UTC by Peter TKATCHENKO
Modified: 2022-02-18 10:26 UTC (History)
4 users (show)

See Also:
bugzilla: maintainer-feedback? (sunpoet)


Note You need to log in before you can comment on or make changes to this bug.
Description Peter TKATCHENKO 2020-06-19 17:40:23 UTC
Multiple ports that depend on graphics/openjpeg cannot be built if both graphics/openjpeg and graphics/openjpeg15 are installed.
The header openjpeg.h is installed to /usr/local/include/openjpeg-2.3 by graphics/openjpeg, but the header with the same name is installed to /usr/local/include by graphics/openjpeg15. When a port is building, both /usr/local/include/openjpeg-2.3 and /usr/local/include are configured as include directories, so the port dependent on graphics/openjpeg tries to include /usr/local/include/openjpeg.h and then fails to build.
Example of such port: graphics/simpleviewer.
Moreover, if a port needs devel/doxygen and graphics/openjpeg in the same time - it cannot be built at all as devel/doxygen (indirectly) depends on graphics/openjpeg15, so graphics/openjpeg15 will be installed before the port and breaks the build.
The port graphics/openjpeg15 must install the header openjpeg.h into /usr/local/include/openjpeg-1.5 and change his pc file accordingly to avoid such conflicts.
Comment 1 alt2600 2022-02-18 03:25:46 UTC
will this ever be addressed or will be forced to start using custom ports trees?

see PR 262008
Comment 2 Dima Panov freebsd_committer 2022-02-18 10:26:33 UTC
Overcomes by events

openjpeg15 installs include into own subdir since f3ba77e14cac05d43caf35100848eeaee3bc64b4