Opened 11 years ago
Closed 7 years ago
#37998 closed defect (fixed)
jasper should not install its config.h
| Reported by: | jeremyhu (Jeremy Huddleston Sequoia) | Owned by: | jmroot (Joshua Root) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.3 |
| Keywords: | Cc: | ||
| Port: | jasper |
Description
The jasper port installs ${prefix}/include/jasper/jas_config.h which is picked up by other ports causing them to possibly build differently from intended because of jas_config.h redefining common autoconf macros like VERSION PACKAGE_NAME PACKAGE_VERSION etc.
Change History (3)
comment:1 Changed 8 years ago by jmroot (Joshua Root)
comment:3 Changed 7 years ago by jmroot (Joshua Root)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed as of 1.900.25.
Note: See
TracTickets for help on using
tickets.
To be clear, the issue is not just that the file is installed, but that it is pulled in by jasper.h which provides the public API. That's deliberate since various parts of the API headers use definitions from jas_config.h. Upstream would need to extensively rework all the headers to fix this namespace pollution.