Re: Unable to build XV

On Sep 18, 2022, at 18:37, Dave Horsfall wrote: > >:info:build xvjp2k.c:77:5: error: redefinition of 'jas_getdbglevel' >:info:build int jas_getdbglevel(void) {return 0;} >:info:build ^ >:info:build /opt/local/include/jasper/jas_debug.h:123:5: note: previous > definition is

Re: Unable to build XV

> On 19 Sep 2022, at 4:21 am, Bill Cole > wrote: > > On 2022-09-18 at 21:33:32 UTC-0400 (Mon, 19 Sep 2022 11:33:32 +1000 (EST)) > Dave Horsfall > is rumored to have said: > >> And because XV is broken I can't continue with upgrading following ports > > You can get around that by

Re: Unable to build XV

Something else that worked since back in the day, and is not broken: ImageMagick and its “display” command. Interface is different and not all functionality has parallels (although mostly “display” does more), but an alternative in the hopefully temporary absence of xv. It does not have its own

Re: Unable to build XV

On Sun, 18 Sep 2022, Bill Cole wrote: > > And because XV is broken I can't continue with upgrading following > > ports > > You can get around that by explicitly excluding xv, e.g.: > > port -v upgrade active and not xv Thanks; I must get used to those logical conditions (FreeBSD ports has no

Re: Unable to build XV

On 2022-09-18 at 21:33:32 UTC-0400 (Mon, 19 Sep 2022 11:33:32 +1000 (EST)) Dave Horsfall is rumored to have said: > And because XV is broken I can't continue with upgrading following ports You can get around that by explicitly excluding xv, e.g.: port -v upgrade active and not xv -- Bill

Re: Unable to build XV

If someone wanted to update the xv port to use this repo, that would make it compatible with jasper 3 (among other things): - Josh

Re: Unable to build XV

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

Re: Unable to build XV

On Sun, 18 Sep 2022, Richard L. Hamilton wrote: > I worked around the existing broken xv binary using a symlink for the > library (which if it all gets fixed, I’ll remove by hand as I created it > by hand). [...] Your workaround works fine; thanks! I made a Calendar entry to remind me. I'm

Re: Unable to build XV

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

Re: Unable to build XV

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 /opt/local/lib/libjasper.4.dylib but the new location for

Unable to build XV

Mid-2010 MacBook Pro w/ High Sierra 10.13.6 (as far as it will go) I'll understand if XV is no longer supported (it's quite long in the tooth), but I find it better than GIMP for my requirements. Anyway... ---> Building xv Error: Failed to build xv: command execution failed