Re: Can't migrate mac ports after Monterey -> Sonoma

On Nov 5, 2024, at 22:39, list_email--- wrote: > > But I couldn’t run _any_ port command without generating getting the platform > mismatch error—see my original post. I could not run sudo port migrate. I had > to download the installer for the current base. Yes. The new migration instructions

Re: Can't migrate mac ports after Monterey -> Sonoma

> On Nov 5, 2024, at 8:26 PM, Ryan Carsten Schmidt > wrote: > > The new instructions don't require you to update MacPorts base first so it's > not mentioned there. But I couldn’t run _any_ port command without generating getting the platform mismatch error—see my original post. I could no

Re: Can't migrate mac ports after Monterey -> Sonoma

On Nov 5, 2024, at 16:27, list_email--- wrote: > > I might suggest a link to the installer page on the “Step 0” of the migration > page, https://trac.macports.org/wiki/Migration. There is no "Step 0". There is already a link to the installer from step 2 of the old instructions. The new instr

Re: Can't migrate mac ports after Monterey -> Sonoma

Oops. My mistake. I should have read the instructions more carefully. I might suggest a link to the installer page on the “Step 0” of the migration page, https://trac.macports.org/wiki/Migration. Jerry > On Nov 4, 2024, at 12:40 PM, Ryan Carsten Schmidt > wrote: > > On Nov 4, 2024, at 00:50,

Re: Can't migrate mac ports after Monterey -> Sonoma

On Nov 4, 2024, at 00:50, Saagar Jha wrote: > > This usually means you need to update your MacPorts install. Try downloading > a new installer for your OS and seeing if that helps. Correct. It is step 2 of the old migration procedure.

Re: Can't migrate mac ports after Monterey -> Sonoma

This usually means you need to update your MacPorts install. Try downloading a new installer for your OS and seeing if that helps. > On Nov 3, 2024, at 19:38, list_email--- via macports-users > wrote: > > I have an M1 on which I recently upgraed the os from 12 Monterey to 14

Can't migrate mac ports after Monterey -> Sonoma

I have an M1 on which I recently upgraed the os from 12 Monterey to 14 Sonoma. I don’t have Xcode installed but I do have the latest (Sonoma) version of Command Line Tools; I think it’s 16.1. I need to upgrade macports. I have followed the instructions at https://trac.macports.org/wiki

MacPorts 2.10.2 Sonoma installer updated

Unfortunately, the MacPorts 2.10.2 installer for macOS 14 Sonoma contained a misconfiguration that can cause port builds to fail. Other macOS versions are not affected. A new build of the installer has been uploaded. The version number is unchanged because it is built from exactly the same

Re: Fix: My dovecot install fails after macOS Sonoma 14.5 update and MacPorts update

On May 22, 2024, at 16:25, Gerben Wierda wrote: > > I was able to circumvent this autoconf failure by installing gettext before > installing dovecot, I don't know if that is the best solution, but ot works > (as in, it now installs). Yes that is the solution and I committed it here: https://gi

Fix: My dovecot install fails after macOS Sonoma 14.5 update and MacPorts update

I was able to circumvent this autoconf failure by installing gettext before installing dovecot, I don't know if that is the best solution, but ot works (as in, it now installs). Gerben Wierda (LinkedIn , Mastodon ) R&A IT

My dovecot install fails after macOS Sonoma 14.5 update and MacPorts update

I did my normal upgrade round, that is, update macOS, then a clean update of MacPorts and a reinstall of my port collection. This is generally routine for me. But this now fails at dovecot (which is nasty,. I really need that mail server, now running on the Linux backup server) port -N install

Re: [unable to compile MPICH v4.2.1 with GNU toolchain v13.2.0 @ macOS Sonoma v14.4.1]

On May 13, 2024, at 21:35, Ryan Schmidt wrote: > > What I found before said that the problem had been fixed in gcc 11.1. It was pointed out in that issue today that newer gcc will still experience the problem when in C99 mode. https://trac.macports.org/ticket/69632#comment:11

Re: [unable to compile MPICH v4.2.1 with GNU toolchain v13.2.0 @ macOS Sonoma v14.4.1]

On May 13, 2024, at 10:07, Maxim Abalenkov wrote: > >> If you want to build anything from source on macOS, use clang unless there >> is an extremely good reason to use gcc. > > When you say clang, do you recommend using Apple’s clang or clang from > MacPorts? Whichever you like. Whichever work

Re: [unable to compile MPICH v4.2.1 with GNU toolchain v13.2.0 @ macOS Sonoma v14.4.1]

7 486 486 505 \\ www.maxim.abalenkov.uk > On 13 May 2024, at 14:51, Ryan Schmidt wrote: > > On May 13, 2024, at 05:36, Maxim Abalenkov wrote: >> >> Dear all, >> >> How are you? I hope all is well with you. I need help please. I’m struggling >> to compile MP

Re: [unable to compile MPICH v4.2.1 with GNU toolchain v13.2.0 @ macOS Sonoma v14.4.1]

On May 13, 2024, at 05:36, Maxim Abalenkov wrote: > > Dear all, > > How are you? I hope all is well with you. I need help please. I’m struggling > to compile MPICH v4.2.1 (from source code) with the GNU toolchain v13.2.0 @ > macOS Sonoma v14.4.1. Please see my configuratio

[unable to compile MPICH v4.2.1 with GNU toolchain v13.2.0 @ macOS Sonoma v14.4.1]

Dear all,How are you? I hope all is well with you. I need help please. I’m struggling to compile MPICH v4.2.1 (from source code) with the GNU toolchain v13.2.0 @ macOS Sonoma v14.4.1. Please see my configuration and installation Perl script attached. I also attach a full log of the compilation

Re: How do I reliably expose MacPorts dovecot to the LAN on macOS Sonoma?

t to run various ports on macOS Sonoma (mail server stuff, like postfix, dovecot, installed by MacPorts) and I am running into a problem. From inside the machine itself, everything is fine. I can connect to the ports using ncBut from another machine on my LAN I cannot. It simply times out when I tr

Re: How do I reliably expose MacPorts dovecot to the LAN on macOS Sonoma?

com/@GerbenWierda> > >> On 24 Jan 2024, at 16:18, Gerben Wierda wrote: >> >> Hello people, >> >> I am currently making an attempt to run various ports on macOS Sonoma (mail >> server stuff, like postfix, dovecot, installed by MacPorts) and I am running &g

Re: How do I reliably expose MacPorts dovecot to the LAN on macOS Sonoma?

gt; On 24 Jan 2024, at 16:18, Gerben Wierda wrote: > > Hello people, > > I am currently making an attempt to run various ports on macOS Sonoma (mail > server stuff, like postfix, dovecot, installed by MacPorts) and I am running > into a problem. > > From inside the machine

How do I reliably expose MacPorts dovecot to the LAN on macOS Sonoma?

Hello people, I am currently making an attempt to run various ports on macOS Sonoma (mail server stuff, like postfix, dovecot, installed by MacPorts) and I am running into a problem. From inside the machine itself, everything is fine. I can connect to the ports using nc But from another

Re: net-snmp runtime problems on Sonoma

On Nov 27, 2023, at 12:17 PM, Daniel J. Luke wrote: > I thought I'd ping the list before digging more into this, but on one Sonoma > (14.1.1) host that I monitor via snmp, MacPorts (and apple's) snmpd (from > net-snmp) seems to get stuck using 100% of one cpu core when I w

net-snmp runtime problems on Sonoma

Hi, I thought I'd ping the list before digging more into this, but on one Sonoma (14.1.1) host that I monitor via snmp, MacPorts (and apple's) snmpd (from net-snmp) seems to get stuck using 100% of one cpu core when I walk the host (or query some stuff from HOST-RESOURCES

Sonoma

Sonoma on apple silicon installed with a Case Sensitive file system Easy I thought format as case sensitive then install Install reformats as Case InSensitive then installs Formatting each sub volume ?? Thanks James

Re: Is there anyone who has successfully migrated Macport to Sonoma?

Xcode 14 will refuse to run on Sonoma - it can run if you trick it, but that is not a great way to get working software. —Mark ___ Mark E. Anderson MacPorts Trac WikiPage <https://trac.macports.org/wiki/mark> GitHub Profile <https://github.com/markemer> On Sun,

Re: ruby-select problem - Sonoma

ris F On 22/10/23 7:12 am, Ryan Schmidt wrote: On Oct 20, 2023, at 19:44, Chris F wrote: I have created an appropriate .bash_profile (as described in the Guide) and everything appears normal now. You are using bash on Sonoma? The default shell is zsh. The MacPorts installer is supposed to

Re: ruby-select problem - Sonoma

On Oct 20, 2023, at 19:44, Chris F wrote: > > I have created an appropriate .bash_profile (as described in the Guide) and > everything appears normal now. You are using bash on Sonoma? The default shell is zsh. The MacPorts installer is supposed to detect which shell you use and conf

Re: Clang 17.0.3 fails to build on Sonoma.

Sending a 31MB log to a mailing list is not a great idea.. Please open a trac ticket. https://trac.macports.org/ Chris > On 20 Oct 2023, at 10:11 pm, doa via macports-users > wrote: > > This port was recently outdated, so this seems rather strange. Attached is > the log I received. > > >

Re: ruby-select problem - Sonoma

0 Oct 2023 11:47:01 +1300) Chris F is rumored to have said: On 20/10/23 11:17 am, Chris Jones wrote: On 19 Oct 2023, at 10:58 pm, Chris F wrote:  I've just migrated to Sonoma 14.0 via a clean OS install plus Migration Assistant and I'm now reinstalling my ports one at a time. Por

Clang 17.0.3 fails to build on Sonoma.

Attachment available until Nov 19, 2023 This port was recently outdated, so this seems rather strange. Attached is the log I received. Thank you. Diego Vicioso. Email… viciosodi...@icloud.com Click to Download

Re: ruby-select problem - Sonoma

>>>> On 19 Oct 2023, at 10:58 pm, Chris F wrote: >>>> >>>>  >>>> >>>> I've just migrated to Sonoma 14.0 via a clean OS install plus Migration >>>> Assistant and I'm now reinstalling my ports one at a time. >>>> >>>

Re: ruby-select problem - Sonoma

On 2023-10-19 at 18:47:01 UTC-0400 (Fri, 20 Oct 2023 11:47:01 +1300) Chris F is rumored to have said: On 20/10/23 11:17 am, Chris Jones wrote: On 19 Oct 2023, at 10:58 pm, Chris F wrote:  I've just migrated to Sonoma 14.0 via a clean OS install plus Migration Assistant and I&

Re: ruby-select problem - Sonoma

On 20/10/23 11:17 am, Chris Jones wrote: On 19 Oct 2023, at 10:58 pm, Chris F wrote:  I've just migrated to Sonoma 14.0 via a clean OS install plus Migration Assistant and I'm now reinstalling my ports one at a time. Port ruby31 installed without problems but ruby-select do

Re: ruby-select problem - Sonoma

> On 19 Oct 2023, at 10:58 pm, Chris F wrote: > >  > I've just migrated to Sonoma 14.0 via a clean OS install plus Migration > Assistant and I'm now reinstalling my ports one at a time. > > Port ruby31 installed without problems but ruby-select doesn't

ruby-select problem - Sonoma

I've just migrated to Sonoma 14.0 via a clean OS install plus Migration Assistant and I'm now reinstalling my ports one at a time. Port ruby31 installed without problems but ruby-select doesn't seem to work/be effective - after ruby-select ruby31 runs successfully, command &quo

Migrating After Sonoma Install

:00AM. When I went to bed at 9:00PM it was still cranking away. I have no idea how long it actually took. But, at least 10 hours. This also amazes me. On the other hand, my M1 MBA also has 13 in requested.txt and 148 in myports.txt. On this machine the post-Sonoma migration took about six hours

Re: gfortran and ifort do not work after upgrading to Sonoma

27;, > assuming: macOS > ld: warning: no platform load command found in > '/opt/intel/oneapi/compiler/2022.1.0/mac/bin/intel64/../../compiler/lib/libirc.a[119](sse2_strncmp.o)', > assuming: macOS > ld: warning: no platform load command found in > '/opt/intel/oneapi/compiler

Re: gfortran and ifort do not work after upgrading to Sonoma

/2022.1.0/mac/bin/intel64/../../compiler/lib/libirc.a[126](ssse3_strncpy.o)', assuming: macOS ld: warning: no platform load command found in '/opt/intel/oneapi/compiler/2022.1.0/mac/bin/intel64/../../compiler/lib/libirc.a[158](intel_mic_avx512f_memcpy.o)', assuming: macOS ld: warni

Re: Is there anyone who has successfully migrated Macport to Sonoma?

On 9/10/2023 10:34, Tao Zhang wrote: Hi Josh,  Thanks for your helpful comments. One more question:    gfortran and ifort  do not work after upgrading to Sonoma. see below.  1) Should I upgrade to the latest Xcode15 or old Xcode14 to fix this problem?  2)  It is reported that Xcode15

Re: Is there anyone who has successfully migrated Macport to Sonoma?

Hi Josh,  Thanks for your helpful comments. One more question:    gfortran and ifort  do not work after upgrading to Sonoma. see below.  1) Should I upgrade to the latest Xcode15 or old Xcode14 to fix this problem?  2)  It is reported that Xcode15 does not work well with Macport, right

Re: Is there anyone who has successfully migrated Macport to Sonoma?

1)  For 1. below , should I use Xcode15 or older version? Xcode 15 or later is required on Sonoma.   2) Does the following procedure work? Is there anyone who has successfully migrated Macport to Sonoma? I haven't heard of any problems with the procedure that are specific to S

Is there anyone who has successfully migrated Macport to Sonoma?

Hi,   The following is the Migration procedure as listed in Macport website.   1)  For 1. below , should I use Xcode15 or older version?   2) Does the following procedure work? Is there anyone who has successfully migrated Macport to Sonoma?  3) How long will this migration procedure take

Re: Status of Macports on Sonoma?

this. André-JohnSent from my phone. Envoyé depuis mon téléphone. On 07 Oct 2023, at 18:56, Kevin Horton wrote:On Oct 7, 2023, at 09:59, Chris Jones wrote:Hi,On 7 Oct 2023, at 1:12 am, Kevin Horton wrote:I'm pondering whether I should upgrade to macOS Sonoma now, or continue to wait.  Gene

Re: Status of Macports on Sonoma?

> On Oct 7, 2023, at 09:59, Chris Jones wrote: > > Hi, > >> On 7 Oct 2023, at 1:12 am, Kevin Horton wrote: >> >> I'm pondering whether I should upgrade to macOS Sonoma now, or continue to >> wait. Generally speaking, how well is Macports working

Re: Status of Macports on Sonoma?

> On Oct 7, 2023, at 11:03 AM, Chris Jones wrote: > > Hi, > >> On 7 Oct 2023, at 3:40 pm, Murray Eisenberg >> wrote: >> >>  >>> OnFri, 6 Oct 2023 19:10:39 -0500,Kevin Horton >> <mailto:kevi...@kilohotel.com>> wrote: >>>

Re: X11 and grads do not work after upgrading to Sonoma

I don't have Sonoma, nor Ventura up at the moment, but on Monterey, /usr/X11 is a symlink to /var/select/X11, which is another symlink. In my case, since I have the macosforge.org <http://macosforge.org/> Xquartz installed, it's a symlink to /opt/X11. That is of course not the m

Re: Status of Macports on Sonoma?

> wrote: > >> > >>  > >>> OnFri, 6 Oct 2023 19:10:39 -0500,Kevin Horton > wrote: > >>> > >>> I'm pondering whether I should upgrade to macOS Sonoma now, or > continue to wait. Generally speaking, how well is Macports working on

Re: Status of Macports on Sonoma?

ote: > > Hi, > >> On 7 Oct 2023, at 3:40 pm, Murray Eisenberg >> wrote: >> >>  >>> OnFri, 6 Oct 2023 19:10:39 -0500,Kevin Horton wrote: >>> >>> I'm pondering whether I should upgrade to macOS Sonoma now, or continue to >&

Re: X11 and grads do not work after upgrading to Sonoma

> On 7 Oct 2023, at 4:25 pm, Tao Zhang wrote: > > Hi Chris, > I am using time machine to transfer them from a Mojave Macbook pro to the > present Sonoma machine. > Is there a new version of X11 that can be installed into /usr/X11? Not provided by macports, no. I do not

Re: X11 and grads do not work after upgrading to Sonoma

Hi Chris,  I am using time machine to transfer them from a Mojave Macbook pro to the present Sonoma machine.  Is there a new version of X11 that can be installed into /usr/X11?  Thanks  Tao On 10/7/23 9:16 AM, Chris Jones wrote: Hi, /usr/local and /usr/X11 are not locations macports will

Re: X11 and grads do not work after upgrading to Sonoma

macports xorg-server port. Chris > On 7 Oct 2023, at 4:10 pm, Tao Zhang wrote: > > Hi, > > I have problem in X11 and grads after upgrading to Sonoma. I am using intel > i9 chip. > > see below. > > Do you know how to fix it? > > Thanks > > Tao

X11 and grads do not work after upgrading to Sonoma

Hi,  I have problem in X11 and grads after upgrading to  Sonoma. I am using intel i9 chip.  see below.  Do you know how to fix it?  Thanks Tao “XQuartz” is damaged and can’t be opened. MacBook-Pro-2018:~ 33;grads dyld[6709]: Library not loaded: /usr/X11/lib/libX11.6.dylib   Referenced

Re: Status of Macports on Sonoma?

Hi,On 7 Oct 2023, at 3:40 pm, Murray Eisenberg wrote:OnFri, 6 Oct 2023 19:10:39 -0500,Kevin Horton <kevi...@kilohotel.com> wrote:I'm pondering whether I should upgrade to macOS Sonoma now, or continue to wait.  Generally speaking, how well is Macports working on Sonoma?  I have seen a

Re: Status of Macports on Sonoma?

Hi,On 7 Oct 2023, at 1:12 am, Kevin Horton wrote:I'm pondering whether I should upgrade to macOS Sonoma now, or continue to wait.  Generally speaking, how well is Macports working on Sonoma?  I have seen a surprising small number of issues posted on this list, and am wondering whether that

Re: Status of Macports on Sonoma?

> OnFri, 6 Oct 2023 19:10:39 -0500,Kevin Horton <mailto:kevi...@kilohotel.com>> wrote: > > I'm pondering whether I should upgrade to macOS Sonoma now, or continue to > wait. Generally speaking, how well is Macports working on Sonoma? I have > seen a surprising

Re: Status of Macports on Sonoma?

On Saturday, October 7th, 2023 at 02:10, Kevin Horton wrote: > > > I'm pondering whether I should upgrade to macOS Sonoma now, or continue to > wait. Generally speaking, how well is Macports working on Sonoma? I have seen > a surprising small number of issues posted

Status of Macports on Sonoma?

I'm pondering whether I should upgrade to macOS Sonoma now, or continue to wait. Generally speaking, how well is Macports working on Sonoma? I have seen a surprising small number of issues posted on this list, and am wondering whether that is a good reflection of the status. Thanks,

Re: Unable to build clang-14 under Sonoma

alling MacOS 14 (Sonoma) in > an M1 MacBook Pro (arm), clang-14 failed to build with the following error > message > > make[2]: Leaving directory > `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_llvm-14/clang-14/wor

Unable to build clang-14 under Sonoma

When trying to rebuild my MacPort ports after installing MacOS 14 (Sonoma) in an M1 MacBook Pro (arm), clang-14 failed to build with the following error message make[2]: Leaving directory `/opt/local/var/macports/build

Re: Cannot install emacs on Sonoma, fails while building clang-14

You can install emacs with the “-nativecomp” variant which should skip trying to build clang. Sent from my iPhone > On Sep 27, 2023, at 6:07 PM, doa via macports-users > wrote: > > Hi… > > CAn’t seem to figure this out. Prebuilt binaries are not yet available so > macports is building fro

Cannot install emacs on Sonoma, fails while building clang-14

Hi… CAn’t seem to figure this out. Prebuilt binaries are not yet available so macports is building from source. Looking at the output, make fails with numerous errors generated, mostly related to llvm sanitizer. Thank you. Diego Vicioso. Email… viciosodi...@icloud.com

Re: Sonoma support?

> On 26 Sep 2023, at 10:18 pm, Chris Jones wrote: > >  > >>> On 26 Sep 2023, at 10:05 pm, Dave Horsfall wrote: >>> >>> On Tue, 26 Sep 2023, Chris Jones wrote: >>> >>> B.t.w. Ryan sent a detailed email on this very point only last week. >>> Please go back read the thread “ Timing of MacPo

Re: Sonoma support?

> On 26 Sep 2023, at 10:05 pm, Dave Horsfall wrote: > > On Tue, 26 Sep 2023, Chris Jones wrote: > >> B.t.w. Ryan sent a detailed email on this very point only last week. >> Please go back read the thread “ Timing of MacPorts Support for New >> macOS Versions” before posting any further follo

Re: Sonoma support?

On Tue, 26 Sep 2023, Chris Jones wrote: > B.t.w. Ryan sent a detailed email on this very point only last week. > Please go back read the thread “ Timing of MacPorts Support for New > macOS Versions” before posting any further follow up questions. Odd; I never saw it... Anyone else not see it?

Re: Sonoma support?

26 Sep 2023, at 9:44 pm, Murray Eisenberg >>> wrote: >>> >> So I guess my question should be refined to: When might the Sonoma >> installer become available? > > That is indeed an entirely different question. > >> >>> On Sep 26, 2023, a

Re: Sonoma support?

> On 26 Sep 2023, at 9:44 pm, Murray Eisenberg > wrote: > > So I guess my question should be refined to: When might the Sonoma installer > become available? That is indeed an entirely different question. > >>> On Sep 26, 2023, at 4:42 PM, Chris Jones wrote: &g

Re: Sonoma support?

So I guess my question should be refined to: When might the Sonoma installer become available? > On Sep 26, 2023, at 4:42 PM, Chris Jones wrote: > > > >> On 26 Sep 2023, at 9:38 pm, Murray Eisenberg >> wrote: >> >> But at https://trac.macports.org/wik

Re: Sonoma support?

ng the route installing form git as I prefer to follow base >> development more closely. >> >> Chris >> >>>> On 26 Sep 2023, at 9:24 pm, Murray Eisenberg >>>> wrote: >>>> >>> What is the status of MacPorts support for the just-r

Re: Sonoma support?

low base > development more closely. > > Chris > >> On 26 Sep 2023, at 9:24 pm, Murray Eisenberg >> wrote: >> >> What is the status of MacPorts support for the just-released macOS Sonoma >> (14.0)? >> >> The latest MacPorts installer lis

Re: Sonoma support?

versions. I for one always using the route installing form git as I prefer to follow base development more closely. Chris > On 26 Sep 2023, at 9:24 pm, Murray Eisenberg > wrote: > > What is the status of MacPorts support for the just-released macOS Sonoma > (14.0)? > >

Sonoma support?

What is the status of MacPorts support for the just-released macOS Sonoma (14.0)? The latest MacPorts installer listed at https://www.macports.org/install.php is for Ventura (13.x). --- Murray Eisenbergmurrayeisenb...@gmail.com Mobile (413)-427-5334 503 King Farm Blvd #101