Re: Installation of pandoc failed (MacBook Pro M1 running Sequoia)

> On 1 Feb 2025, at 15:02, Ryan Carsten Schmidt wrote: > > On Feb 1, 2025, at 06:24, Artemio González López wrote: >> >> It seems to me that the problem is that the directory >> >> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports

Installation of pandoc failed (MacBook Pro M1 running Sequoia)

I am trying to update pandoc from 3.4_1 to 3.6.2_0 on a 2020 MacBook Pro 15” running Sequoia 15.3. However, installation fails with the following error message: ---> Configuring pandoc DEBUG: Preferred compilers: clang macports-clang-18 macports-clang-17 macports-clang-16 macports-clang-15 mac

Re: failed migration to Sequoia

> On 21 Sep 2024, at 02:58, Joshua Root wrote: > > On 21/9/2024 03:36, Artemio González López wrote: >> I just ran port selfupdate, but the only outdated port it found is xorg- >> libXi (which I updated). I guess it is not worth to give port restore — >> last another try, since the problemati

Re: failed migration to Sequoia

> On 20 Sep 2024, at 01:07, Joshua Root wrote: > >> >> Unfortunately, after executing supo port restore —last I got exactly the >> same error as before (libgcc14 and lib sodium failed, and cause several >> ports, like emacs-app, not to compile). I do not know what else to do. Could >> execut

Re: failed migration to Sequoia

> On 19 Sep 2024, at 20:46, Joshua Root wrote: > > On 19/9/2024 18:30, Artemio González López wrote: >> Thanks, Josh! In fact, I renamed the /Library/Developer/CommandLineTools and >> got most of my ports to succesfully build after executing “sudo port restore >> —last”. Unfortunately, there

Re: failed migration to Sequoia

> On Sep 18, 2024, at 5:29 PM, Joshua Root wrote: > > Artemio González López wrote: > >> Yesterday I tried to migrate my Sonoma MacPorts installation to the newly >> installed Sequoia on a 2019 M1 MacBook Pro 13”. I used the new procedure, >> i.e., >> >> sudo port migrate >> >> The procedu

failed migration to Sequoia

Hi everybody, Yesterday I tried to migrate my Sonoma MacPorts installation to the newly installed Sequoia on a 2019 M1 MacBook Pro 13”. I used the new procedure, i.e., sudo port migrate The procedure produced the following errors: Migration finished with errors. The following ports coul

Problem with jupyter-notebook

I am having a problem with the jupyter-notebook port (both 3.11 and 3.12) under MacOS 14.5 (Sonoma) on an M1 13” MacBook Pro. More specifically, jupyter-notebook launches and allows me to navigate my hard disk. However, when I click on a notebook to try to edit/run it a new tab is opened in Safa

jupyter-notebook and jupyter-lab 3.11 stopped working

Both of these python ports stopped working recently (I’m running Sonoma on a 15” 2021 MacBook Pro). For jupyter-lab, the error I get when I try to run it is: raceback (most recent call last): File "/opt/local/bin/jupyter-lab-3.11", line 33, in sys.exit(load_entry_point('jupyterlab==3.0.13'

Re: problem with py311-scipy on M1 MacBook Pro

I just realized that my problem could exactly be the one reported in ticket #68329 (py311-scipy @1.10.1_0+gfortran+openblas not building on Sonoma apple silicon). Indeed, I just spotted the following lines in my main.log: :info:build ld: duplicate LC_RPATH '/opt/local/lib/libgcc' in '/opt/local

problem with py311-scipy on M1 MacBook Pro

When I tried to install py311-scipy on an M1 MacBook Pro running the latest macOS (Sonoma 14.0), installation failed with (among others) the following error message: :debug:main Starting logging for py311-scipy @1.10.1_0+gfortran+openblas :debug:sysinfo macOS 14.0 (darwin/23.0.0) arch arm :debug

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/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarball

Python 3.10 fails to build (Ventura 13.2.1, Xcode 14.2)

Since last week or so, I haven’t been able to update my python 3.10. I believe the relevant error is the following: make[1]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_python310/python310/work/Python-3

question on py-simpy

I just installed py39-simpy, without realizing that py-simpy was actually installed. So now port installed py\*-simpy produces The following ports are currently installed: py-simpy @4.0.1_1 (active) py39-simpy @4.0.1_0 (active) Is this a conflict? Should I uninstall one of the two ports?

Re: macports-users Digest, Vol 195, Issue 12

> On Nov 21, 2022, at 1:00 PM, macports-users-requ...@lists.macports.org > wrote: > > On Nov 10, 2022, at 11:56, Artemio Gonz?lez L?pez wrote: >> >> After installing the 13.0.1 update on my M1 MacBook Pro I emacs.app crashes >> on launch. Appa

Re: Emacs.app does not run after upgrade to macOS 13.0.1

> On 10 Nov 2022, at 18:56, Artemio González López wrote: > > After installing the 13.0.1 update on my M1 MacBook Pro I emacs.app crashes > on launch. Apparently, the problem is that it cannot find a library: > > Crashed Thread:0 > > Exception Type:EXC_CRASH (SIGABRT) > Except

Re: C compiler not found after upgrade to macOS 13.0.1

fu, Artemio > >> On 10 Nov 2022, at 7:02 pm, Artemio González López via macports-users >> wrote: >> >>  >>> On 10 Nov 2022, at 18:52, Artemio González López wrote: >>> >>> After upgrading to macOS 13.0.1 (on an M1 MacBook Pro), port cannot

Re: C compiler not found after upgrade to macOS 13.0.1

> On 10 Nov 2022, at 18:52, Artemio González López wrote: > > After upgrading to macOS 13.0.1 (on an M1 MacBook Pro), port cannot find any > C compiler: > > checking for gcc... /opt/local/bin/clang-mp-14 > checking whether the C compiler works... no > configure: error: in > `/opt/local/var/ma

Re: Emacs.app does not run after upgrade to macOS 13.0.1

> On 10 Nov 2022, at 19:57, Sriranga Veeraraghavan > wrote: > > Hi, > > On my Monterey (12.6.1) system, 'port provides' says that the missing library > is provided by the 'icu' port: > > $ port provides /opt/local/lib/libicui18n.71.dylib > /opt/local/lib/libicui18n.71.dylib is provided by:

Re: C compiler not found after upgrade to macOS 13.0.1

> On 10 Nov 2022, at 19:33, Chris Jones wrote: > > > >> On 10 Nov 2022, at 5:53 pm, Artemio González López via macports-users >> wrote: >> >> After upgrading to macOS 13.0.1 (on an M1 MacBook Pro), > > Upgrading from what OS ? Sorry, fro

Emacs.app does not run after upgrade to macOS 13.0.1

After installing the 13.0.1 update on my M1 MacBook Pro I emacs.app crashes on launch. Apparently, the problem is that it cannot find a library: Crashed Thread:0 Exception Type:EXC_CRASH (SIGABRT) Exception Codes: 0x, 0x Termination Reason:

C compiler not found after upgrade to macOS 13.0.1

After upgrading to macOS 13.0.1 (on an M1 MacBook Pro), port cannot find any C compiler: checking for gcc... /opt/local/bin/clang-mp-14 checking whether the C compiler works... no configure: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_rele

Re: macports-users Digest, Vol 194, Issue 22

> On 29 Oct 2022, at 14:00, macports-users-requ...@lists.macports.org wrote: > > > >> On Oct 28, 2022, at 8:16 PM, Andreas Skarlatoudis > > wrote: >> >> :notice:patch ---> Applying patches to aquaterm >> :info:patch ---> Applying no-NSMailDelivery.patch >> :debug

problems recompiling ports for Ventura

When trying to recompile my ports after upgrading to Ventura (as per the instructions in https://trac.macports.org/wiki/Migration) I ran into the following problems: 1) Installation of py310-jupyter failed with the following error message: Error: Failed to activate py310-jupyter: Image error:

Re: Questions on migration to macOS Ventura

(or >>> e.g. update at some later time) your macports installation. >>> >>> Cheers Chris >>> >>>>> On 25 Oct 2022, at 6:58 pm, Artemio González López via macports-users >>>>> wrote: >>>>> >>>>

Re: Questions on migration to macOS Ventura

orts installation. > > Cheers Chris > >> On 25 Oct 2022, at 6:58 pm, Artemio González López via macports-users >> wrote: >> >>  >> I just upgraded to macOS Ventura, and would like to migrate my MacPorts >> installation accordingly. However,

Questions on migration to macOS Ventura

I just upgraded to macOS Ventura, and would like to migrate my MacPorts installation accordingly. However, when following the instructions at https://trac.macports.org/wiki/Migration I realized that the MacPorts installer for Ventura has not been released yet. My questions are the following: 1.

py39-nbconvert fails to build on Catalina

I got the following error when trying to build py39-nbconvert on a 2014 27” iMac running the latest version of Catalina (10.15.7). The error I got (from main.log) is the following: :info:build Executing: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macpo

port diagnose output on M1 MacBook Pro

After executing “port diagnose” in my 2020 13” MacBook Pro running the latest version of the operating system (Monterrey 12.1.3, I believe) I got the following output: Warning: objc[10836]: Class AppleTypeCRetimerRestoreInfoHelper is implemented in both /usr/lib/libauthinstall.dylib (0x1f6af5eb

Re: do I have to reinstall my ports after upgrading to Monterey?

> On 31 Oct 2021, at 16:46, Christopher Jones wrote: > > > Yes you do. You should always follow the migration instructions under > > https://trac.macports.org/wiki/Migration > <https://trac.macports.org/wiki/Migration> > > Chris > >> On 31 Oct 20

do I have to reinstall my ports after upgrading to Monterey?

I just installed macOS 12.0.1 on an M1 MacBook Pro 13” from last year, and I was wondering if it’s necessary to reinstall all my ports (which I installed under Big Sur) after the update (they seem to be running just fine). Thanks a lot in advance, Artemio Artemio Gonzalez Lopez artem...@mac.c

Spyder fails to install in M1 MacBook Pro

When trying to install py-spyder in my M1 MacBool Pro 13” installation fails with the error message quoted below. Is this a known problem? Can anybody suggest a possible fix/workaround? Thanks in advance, Artemio === Apple clang version 13.0.0 (clang-1300.0.2

Re: What is the best way of installing Python's scientific libraries in MacPorts?

> On Oct 6, 2021, at 12:20 AM, Ryan Schmidt wrote: > > On Oct 4, 2021, at 08:43, Artemio González López wrote: > >> 1. Should I activate python39 and decativate python37 before installing the >> 3.9 versions fo numpy, scipy and matplotlib? > > It's not necessary. MacPorts handles dependencie

Re: What is the best way of installing Python's scientific libraries in MacPorts?

> On Oct 4, 2021, at 10:57 PM, Christopher Jones > wrote: > > > >> On 4 Oct 2021, at 9:18 pm, Artemio González López via macports-users >> > <mailto:macports-users@lists.macports.org>> wrote: >> >>> >> >> Ciao Gius

Re: What is the best way of installing Python's scientific libraries in MacPorts?

> On Oct 4, 2021, at 4:24 PM, Giuseppe 'ferdy' Miceli > wrote: > > ciao artemio, > >> Hi, Giuseppe, > > > >> So my questions are: >> >> 1. Should I activate python39 and decativate python37 before installing the >> 3.9 versions fo numpy, scipy and matplotlib? > > I

Re: What is the best way of installing Python's scientific libraries in MacPorts?

> On Oct 4, 2021, at 12:26 PM, Giuseppe 'ferdy' Miceli wrote: > > ciao artemio, > >> On 3 Oct 2021, at 23:05, Artemio González López via macports-users >> > <mailto:macports-users@lists.macports.org>> wrote: >> >> I have

What is the best way of installing Python's scientific libraries in MacPorts?

I have installed the python37 port, and would like to install the scientific libraries numpy, scipy, and matplotlib, and also jupyter. I installed by hand the ports py-numpy, py-scipy, py-matplotlib, py-jupyter (without specifying a version), and port installed python39, py39-jupyter and the 3

Re: Port aom failed to build on MacBook Pro 13 M1 (Big Sur 11.2.3)

> On 2 Apr 2021, at 00:43, Ryan Schmidt wrote: > > > > On Apr 1, 2021, at 17:05, Artemio González López wrote: > >> When I tried to build the aom port in my MacBook Pro 13 M1 running Big Sur >> 11.2.3 I got the following error: >> >> make[1]: Leaving directory >> `/opt/local/var/macports/b

Port aom failed to build on MacBook Pro 13 M1 (Big Sur 11.2.3)

When I tried to build the aom port in my MacBook Pro 13 M1 running Big Sur 11.2.3 I got the following error: make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_aom/aom/work/build' make: *** [all]

Re: MacPort's rsyncd error messages after changing ssh port

> On Feb 19, 2020, at 12:23 PM, Ryan Schmidt wrote: > > On Feb 17, 2020, at 13:32, Artemio González López wrote: > >> After changing the sshd port from 22 to a non-standard (high) number, I’ve >> noticed that my system.log is flooded with error messages like the >> following, coming from MacP

MacPort's rsyncd error messages after changing ssh port

After changing the sshd port from 22 to a non-standard (high) number, I’ve noticed that my system.log is flooded with error messages like the following, coming from MacPort’s rsync daemon: Feb 17 20:11:05 my-compuer-name com.apple.xpc.launchd[1] (org.macports.rsyncd[18457]): Service exited with

Re: possible malware in db48 port

Thank you all. I have just put these two files in Bitdefeneder's exception list. Artemio Gonzalez Lopez artem...@mac.com smime.p7s Description: S/MIME cryptographic signature

possible malware in db48 port

Bitdefender has flagged two files from the db48 MacPorts port installed in my Mac, namely /opt/local/lib/db48/libdb_cxx-4.8.dylib /opt/local/var/macports/software/db48/db48-4.8.30_4.darwin_17.x86_64.tbz2 which seem to be infected by something called Gen:Variant.Application.MAC.Koiot.575 Does t