Re: Desolate Condition ==> ImageMagick 7.x requests

> For example, ImageMagick is at 7.0.10 in brew, but still at 6.9.11 in ports. For years now people have requested a 7.x version of this in MacPorts...Ryan could probably update it in less than 5 minutes. But there is some reason I never bothered to read through why that is a Bad Idea. Doesn't

Re: Desolate Condition ==> ImageMagick 7.x requests

The first Bad Idea reason I imagine is if some port(s) that depend on ImageMagick don't play nice with the latest version, to the point where having them work is preferable to having ImageMagick be current. A counter-argument would be HEIF support (which a quick google suggests was added in Ima

Re: Desolate Condition ==> ImageMagick 7.x requests

It looks like https://trac.macports.org/ticket/51310 covers quite a bit of discussion starting five years ago and as recent as three weeks. Someone has a private ImageMagick-7 port that people can use locally, if they wish (bottom comment on ticket). But

Re: Desolate Condition

> On Jan 26, 2021, at 12:02 PM, Tom wrote: > > I am using Big Sur 11.1 > Which macOS are you using? > I am installing new ports. > > tom@Toms-Mac-Pro ~ % port diagnose > Warning: No Xcode version info was found for your OS version. > Warning: found dylibs in your /usr/local/lib directory. These

Re: Desolate Condition ==> ImageMagick 7.x requests

On Jan 26, 2021, at 11:50, Richard L. Hamilton wrote: > A counter-argument would be HEIF support (which a quick google suggests was > added in ImageMagick 7.0.7-22). HEIF/HEIC support was added to the MacPorts ImageMagick (6) port in December 2019. https://github.com/macports/macports-ports

Fwd: Build Failure on ports-10.10_x86_64: ixion

Might this be fixed by a -std= flag? I don't get this error on Big Sur. -- Forwarded message - From: Date: Tue, Jan 26, 2021, 13:48 Subject: Build Failure on ports-10.10_x86_64: ixion To: Cc: Status: Failure Build slave: ports-10.10_x86_64 Full logs: https://build.macpo

Re: Build Failure on ports-10.10_x86_64: ixion

On Jan 26, 2021, at 13:41, Andrew Udvare wrote: > Might this be fixed by a -std= flag? I don't get this error on Big Sur. The error is: model_context.cpp:20:39: error: unknown type name 'nullptr_t'; did you mean 'std::nullptr_t'? Maybe the error message is right and it should be using "std:

Re: Start the Xserver automatically

On Mon, Jan 25, 2021 at 12:00:23AM -0600, Ryan Schmidt wrote: > On Jan 24, 2021, at 22:35, Tong Sun wrote: > > > I checked the x11.app's preference, but it seems to be missing the > > capability to start the Xserver automatically when user logs in. > > > > Is it so? Any plan to add it? > > Th

fetching distfiles for p5.30-libapreq2 hanging or crashing macOS Big Sur

I’m migrating MacPorts from Catalina to Big Sur (11.1), following the usual procedure (uninstalled all ports before upgrading; installed CLT for Xcode 12.3; installed base system for Big Sur). I’ve successfully installed a number of ports, including perl5.30. But now when I execute su

Re: Desolate Condition

Please be sure to copy the macports-users mailing list with your replies. I’m not familiar with any of the desktop environments that you’ve listed. I do note that we have around 300 entries each in the Gnome and KDE sections of our repository: https://ports.macports.org/ports/category/kde/ ht

Re: Start the Xserver automatically

On Tue, Jan 26, 2021 at 8:22 PM raf wrote: > > On Mon, Jan 25, 2021 at 12:00:23AM -0600, Ryan Schmidt > wrote: > > > On Jan 24, 2021, at 22:35, Tong Sun wrote: > > > > > I checked the x11.app's preference, but it seems to be missing the > > > capability to start the Xserver automatically when us

Re: Build Failure on ports-10.10_x86_64: ixion

Ryan Schmidt wrote: On Jan 26, 2021, at 13:41, Andrew Udvare wrote: Might this be fixed by a -std= flag? I don't get this error on Big Sur. The error is: model_context.cpp:20:39: error: unknown type name 'nullptr_t'; did you mean 'std::nullptr_t'? Maybe the error message is right and it sh