jasper was recently updated to provide version 3.x, previously it was 2.x
A new port jasper2 was made providing the older version, and ports like xv updated to use it. Unfortunately though it appears if you attempt to build xv whilst having the newer jasper port installed it opportunistically finds and uses headers from that port, and thus ends up with conflicting defines. Until someone provides a fix for this, you can work around it by deactivating jasper sudo port deactivate jasper Then build xv. You can then reactivate jasper safely afterwards. Chris > On 19 Sep 2022, at 1:44 am, Dave Horsfall <d...@horsfall.org> wrote: > > On Sun, 18 Sep 2022, Richard L. Hamilton wrote: > >> I’ve not only seen that across various macOS versions, but something >> else broke the existing xv because one of the ports the older version >> depended on changed where it keeps some libraries. Specifically, the >> older version of xv expects > > [..] > > Grumble... So I see :-( > > I like XV (been using it since SunOS) so I'll try your fix. > > -- Dave
