Re: Definitions out of date?

Update to 2.11.4 just now, and ran "port upgrade outdated: Warning: port definitions are more than two weeks old, consider updating them by running 'port selfupdate'. Nothing to upgrade. ---> Scanning binaries for linking errors ---> No broken files found.

MacPorts 2.11.4 has been released

The MacPorts Project is pleased to announce the release of version 2.11.4. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new

Re: Failed to build wxWidgets-3.2

Running my weekly update, I get: Error: Failed to destroot wxWidgets-3.2: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_aarnet.au.rsync.macports.org_pub_macports_graphics_wxWidgets-3.2/wxWidgets-3.2/main.log for details. Error: Prob

Re: port mpkg error

H. D. Saviolaan 8 1700 Dilbeek T. : 00 32 02 466 5000 On 24 Jul 2025, at 20:43, Joshua Root wrote: I'm trying to create a custom Barman 3.14.1 mpkg using the latest MacPorts version (macOS - Apple Silicon). When building I get the following error: Error:

port mpkg error (was: ditem_95)

I'm trying to create a custom Barman 3.14.1 mpkg using the latest MacPorts version (macOS - Apple Silicon). When building I get the following error: Error: Failed to mpkg barman: can't read "ditem_95 6.5 0": no such variable Checking the logs it seems to be caused by: debug:mpkg Sourcing Por

MacPorts 2.11.3 has been released

The MacPorts Project is pleased to announce the release of version 2.11.3. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new i

MacPorts 2.11.2 has been released

The MacPorts Project is pleased to announce the release of version 2.11.2. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new in

MacPorts 2.11.1 has been released

The MacPorts Project is pleased to announce the release of version 2.11.1. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new ins

MacPorts 2.11.0 has been released

The MacPorts Project is happy to announce that the 2.11.0 version has now been released. It is available via the usual methods: - selfupdate if you already have MacPorts installed - package installers [1] for macOS 15 Sequoia and all older releases back to Mac OS X 10.5 Leopard

MacPorts 2.11.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.11.0-rc1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) If no s

Re: Dovecot will not compile (Sonoma 14.7.5, MacPorts 2.10.7, Intel). cstddef.h not found.

On 26/6/2025 01:57, Gerben Wierda wrote: :info:build /opt/local/include/CLucene/SharedHeader.h:57:10: fatal error: 'cstddef' file not found :info:build57 | #include //need this for wchar_t, size_t, NULL :info:build | ^ Is there something I can do to fix this?

Re: MacPorts 2.11.0-beta1 now available for testing

Well, it's been a week and no bugs have been reported against the beta. Either this is a flawless release with no regressions, or we could use some more testing. :) Historically there have usually been a few issues that get reported right after the final release, so it would be nice to catch t

MacPorts 2.11.0-beta1 now available for testing

Source code and pkgs for MacPorts 2.11.0-beta1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) There

Re: selfupdate failure: rsync: [sender] change_dir "/release/tarballs" (in macports) failed: Permission denied (13)

Dave Horsfall wrote: On Fri, 30 May 2025, Clemens Lang wrote: >/No, see https://trac.macports.org/ticket/72556. / Hmmm; that could explain my own problem... Probably not, since the problem in the ticket only existed for a few hours and was not related to DNS. - Josh

Re: What's up with Macports' DNS?

Happened twice now (but works some time later): mackie$ sudo port -v selfupdate ---> Checking for newer releases of MacPorts % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft

MacPorts 2.10.7 has been released

The MacPorts Project is pleased to announce the release of version 2.10.7. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For ne

Re: py39-pdm-backend fails to build in Sonoma 14.7.6

Since a few days ago the py39-pdm-backend package fails to build under Sonoma 14.7.6 using Macports 2.10.5 or 2.10.6 :/debug:build system: cd /"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-pdm-backend/py39-pdm-backend/

MacPorts 2.10.6 has been released

The MacPorts Project is pleased to announce the release of version 2.10.6. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new

Re: which texlive bit to get a particular package

I have once again lost track of the list of which packages are installed with various texlive ports. In particular, I expected that texlive-math-science would contain esint.sty. It apparently does not. How now I need to figure out what else I need to install to get that package? I thought

Re: Ventura Installation fails in /opt/ports

Something is looking for '/opt/local/libexec/macports/lib/sqlite3.44.2/libsqlite3.44.2.dylib’ , but that looks like a hardcoded path, because I’m not installing into /opt/local. That dylib is present in /opt/ports. From the backtrace, it's Pextlib. Confirm with `otool -L /opt/ports/libexec/

Re: flang-20 port is building VERY SLOWLY, "memory pressure" (Activity monitor) is very high

Building flang has always been CPU+RAM intensive, but it looks like it is thrashing now. Is there a way to make it go single threaded? I have like ten "stuck" clang processes... A better solution would be to set build.mem_per_job to something higher in the port. It defaults to 1024 (MB) an

Re: Failed to activate imath

On 11/2/2025 01:10, Christoph Kukulies wrote: I ran the sudo port upgrade, and it failed: Well, qemu failed; the other 726 ports including imath and openexr succeeded. :) As usual, please file a ticket if there isn't already one for the qemu build failure that you're seeing. - Josh

Re: Failed to activate imath

>/Am 09.02.2025 um 05:40 schrieb Joshua Root <https://lists.macports.org/mailman/listinfo/macports-users>>: />//>/Running 'sudo port migrate' may be the most reliable way to upgrade a very old installation./ Thanks. This will probably a monster job, re-installin

Re: Failed to activate imath

---> Activating imath @3.1.12_0 Error: Failed to activate imath: The following ports have active files that conflict with imath's: ilmbase @2.3.0_1 /opt/local/lib/libImath.dylib This is . According to one of the imath maintainers in the ticket, it on

Re: Problem after upgrade to 2.10.5

On 1/2/2025 00:16, Jurgen Defurne wrote: It is actually 'port -df selfupdate' (described at the end of the ticket) that you need to do. It seems that this starts something more elaborate, because there is also a whole of building going on. It's no more elaborate than a normal selfupdate when t

Re: Problem after upgrade to 2.10.5

On 31/1/2025 22:58, Riccardo Mottola wrote: I get the stupid error right while executing selfupdate. I issued it several times, I always got the error with the same ID as duplicate. If issue outdated, instead, I get consistently another ID as duplicate port outdated even shows a couple of ports

Re: Problem after upgrade to 2.10.5

Riccardo Mottola wrote: during/after upgrade I got this: $ port outdated Error: process_cmd failed: sqlite error: another row available (100) while executing query: SELECT cxx_stdlib FROM registry.ports WHERE id=1184 Jurgen Defurne wrote: Yesterday evening I upgraded to macports 2.10.5. After

Re: mpkg build with Apple Silicon

Hello, We've build a few packages using the mpkg command on an Apple Silicon Mac. When we want to install any of these packages, Rosetta 2 installation is required. We want to avoid using Rosseta 2, if there a way of forcing the architecture to arm64 when building a mpkg? Unfortunately Apple's

Re: Transferring Port Across Systems

Anthony M. Agelastos wrote: I have 2 macOS systems on ARM64. There are some Ports I'm able to build on System A that I cannot on System B. I would like to transfer the build from A to B. This doesn't happen often and is only for a few Ports. So, setting up a binary mirror and all of that is sign

Security issue in MacPorts 2.10.4 and older

MacPorts versions 2.10.4 and older contain a vulnerability that can allow a compromised rsync mirror to add Portfiles to the synced ports tree, thus allowing arbitrary code to be executed when those Portfiles are parsed. (Note that we currently have no reason to believe that any of our mirrors

Re: Should preferred_hosts honour relative ordering within the line?

Normally, MacPorts tries hosts in ping order. Without having looked at the code, I assume the same applies to preferred hosts: that they are tried in ping order, before any of the other hosts. The list of download URLs is indeed sorted by host ping time. A stable sort algorithm is used, so ho

Re: How to Reinstall postgresql96 for Data Migration; Was: Time to delete old PostgreSQL from MacPorts?

The EOL versions should definitely be deprecated, but removal was only on the table because no one was willing to do the work to backport the patches to get them building again. If you are, then great! The old versions are indeed useful to have available for the purpose of getting your data int

MacPorts 2.10.5 has been released

The MacPorts Project is pleased to announce the release of version 2.10.5. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new

Re: Graphviz build fails

David Nicholls wrote: With the latest Sonoma 14.7.1 on an Intel Mac, the most recent Xcode tools and Macports 2.10.4 self updated, I ran port upgrade outdated, and after a few port upgrades, I got this message: sudo port upgrade outdated ---> Computing dependencies for graphviz ---> Fetchin

MacPorts 2.10.4 has been released

The MacPorts Project is pleased to announce the release of version 2.10.4. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new i

MacPorts 2.10.3 has been released

The MacPorts Project is pleased to announce the release of version 2.10.3. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new in

Re: Foiled Again - Part 3 Addendum

Michael Newman wrote: So, I decided to run reclaim and try again with ffmpeg. But this time the list of dependencies was huge: [long list of dependencies] Yes, ffmpeg has a lot of dependencies and even more when building from source. Reclaim may have removed some of the latter because they'r

Re: Foiled Again - Part 3 Addendum

Michael Newman wrote: Anyway, I was able to get MacPorts fully working by: sudo rm -rf /Library/Developer/CommandLineTools You don't have to fully remove the CLTs to fix the problem, just /Library/Developer/CommandLineTools/usr/include/c++. Install CLT 16 from the DMG available from ​ht

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 sou

Re: Foiled Again

On 2/10/2024 15:06, Michael Newman wrote: I did my best with the bug report. I had no idea what to put in the comments section. The Description field is for any additional information or analysis that is not present in the log and too long to put in the Summary. If you don't have anything to

Re: Foiled Again

Michael Newman wrote: This morning I upgraded my 2019 iMac to Sequoia and then did a port migrate. I think everything went OK, except for the following: The following ports could not be restored: - nbsmtp Failed: Unable to execute target 'activate' for port nbsmtp - see its

MacPorts 2.10.2 has been released

The MacPorts Project is pleased to announce the release of version 2.10.2. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new ins

Re: segmentation fault during an install

Just trying again seems to have eliminated the curl issue (after cleaning libmagic and first installing some other ports that were missed on the migrate sweep). Typically the crash only happens when connecting to an FTP site after having connected to a HTTP/2 site. So availability of binaries

Re: segmentation fault when fetching from ftp

Ryan Carsten Schmidt wrote: On Sep 27, 2024, at 16:51, Murray Eisenberg wrote: >//>/Does installing the MacPorts version of curl accomplish anything in this regard? / Not unless you build MacPorts from source and configure it to use MacPorts curl but that's not recommended because your MacPor

Re: Requested Ports

Michael Newman wrote: I did what Arno suggested (thank you) and I now have a requested.txt file that, as far as I can tell, is a good representation of both: • The ports I migrated to this machine when I first set it up last October. • The ports that I later installed. What I still don’t unde

Re: several ports cannot be installed due to a Perl circular dependency hell...

Error: The following dependencies were not installed because all of them have unmet dependencies (likely due to a dependency cycle): p5.34-authen-sasl p5.34-net-smtp-ssl p5.34-cgi p5.34-pod-coverage-trustpod p5.34-test-simple p5.34-pod-eventual p5.34-mixin-linewise p5.34-sub-exporter p5.34-data-op

Re: Tcl mess

Ryan Carsten Schmidt wrote: On Sep 23, 2024, at 03:29, Christoph Kukulies wrote: > > How can I overcome this? I'm not sure. I haven't seen this before. It almost sounds like the selfupdate didn't fully work and didn't fully update the bundled copy of Tcl. Try installing MacPorts using the i

Re: Migration Errors after Sequoia

I still can’t install msmtp because: Error: Failed to build gss: command execution failed I hesitate to file a bug report on this problem because it appears that there is already a bug report on gss (#70869), but I can’t tell if mine would be a duplicate of that. The only way to be certain i

Re: failed migration to Sequoia

On 21/9/2024 21:18, Artemio González López wrote: julia :info:build curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443 :info:build make[1]: *** [/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_macports_r

Re: failed migration to Sequoia

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 problematic por was libgcc14, which hasn’t¡t been updated. Am I right

Re: failed migration to Sequoia

On 20/9/2024 08:27, Artemio González López wrote: Before reading your message, I deleted the directory /Library/Developer/ CommandLineTools and reinstalled the Command Tools for Xcode 16 (which I also have installed) from scratch using the dmg at the Developer website. This should be equivale

Re: failed migration to Sequoia

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 is still a problem with libgcc14 that prevents emacs-app to

Re: what setting to use to force only arm64 (Apple Silicon) binaries/libraries, no universal ports?

Clearing universal_archs in macports.conf will disable universal entirely. Some ports that don't support arm64 may still install as x86_64 if they don't require any universal dependencies. - Josh

Fix for CLTs C++ issue

For those who haven't been following the ticket, we've determined that the problem is caused by the CLTs installer not deleting everything left over from older versions when updating, combined with some unfortunate logic in how clang++ constructs its include paths. Fresh CLTs installations are

Re: failed migration to Sequoia

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 procedure produced the following errors: <...> It seems that there is currently a pr

Caution: CLTs appear to be broken on Sequoia

See for the details. It may be a good idea to wait a while to upgrade. If you have to use MacPorts on Sequoia right now, it may work best to install only Xcode 16 without the Command Line Tools. - Josh

Re: Pseudo-Portname Selectors

When I run port echo depends:vim neovim-qt p5-text-vimcolor py-neovim rails.vim libvmaf gutils-suite-core mpvim neovim-remote nvimpager vim2html vimpager dosfstools (12 ports are listed) But when I run port echo rdepends:vim dosfstools gutils-suite gutils-suite-core gutils-suite-extra libvma

Re: Dependencies/Dependents

bernard.remacle wrote: What is the meaning of ‘rdepends’? (The manual page on port(1) is a little difficult to understand): I understand ‘r’ is the prefix for recursive. What is the difference between ‘rdepends’ and ‘rdependentof’? The rdepends: selector is the recursive version of depends:,

Re: Doubly Active PHP

When I type ‘port installed’, I notice I have 2 php8* ports (php82 @8.2.23_0 and php83 @8.3.11_0) and both are active. Here is the list of php ports I have: php82 @8.2.23_0+libedit (active) php82-gd @8.2.23_0 (active) php82-mbstring @8.2.23_0 (active) php82-mcrypt @1.0.7_0 (active)

Re: 2.10.1 macports SQL error on 10.6

Bill Cole wrote: On 2024-09-06 at 22:25:07 UTC-0400 (Sat, 7 Sep 2024 12:25:07 +1000) Joshua Root https://lists.macports.org/mailman/listinfo/macports-users>> is rumored to have said: [...] > First install the macports.sqlext port. Then run this command (all one > line): >

Re: 2.10.1 macports SQL error on 10.6

On 7/9/2024 02:14, Riccardo Mottola wrote: The first step toward fixing it is to find out which ports' db rows are affected. Try running this: sqlite3 /opt/local/var/macports/registry/registry.db "select * from ports where id=726" sqlite3 /opt/local/var/macports/registry/registry.db "select

Re: 2.10.1 macports SQL error on 10.6

on my MacBook (64bit) after upgrading to macports 2.10.1, "port selfupdate" yields: ---> Checking for newer releases of MacPorts MacPorts base version 2.10.1 installed, MacPorts base version 2.10.1 available. ---> MacPorts base is already the latest version ---> Updating the ports tree The p

file conflict between qemu and dtc

Kenneth Wolcott wrote: circular dependency between qemu and dtc This is not a circular dependency. Qemu (now) depends on dtc, dtc does not depend on qemu. self-update qemu fails due to conflict with dtc deactivating dtc then trying to update qemu fails because it activates dtc The prev

MacPorts 2.10.1 has been released

The MacPorts Project is pleased to announce the release of version 2.10.1. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new inst

Re: Platform mismatch error

On 15/8/2024 17:04, Raoul MEGELAS wrote: On 15 Aug 2024, at 00:48, Joshua Root wrote: Could you please show the output of the following commands in the shell you use to run the port command? sysctl sysctl.proc_translated => 1 echo $SHELL => /bin/zsh lipo -info $SHELL => Architectur

Re: Platform mismatch error

On 15/8/2024 02:35, Raoul MEGELAS wrote: Hello Joshua Please see the screenshot of info: It seems to me than open rosetta is unchecked. Another point: The shell is zsh (native on install). I will try your suggestions and report. Bests Raoul Could you please show the output of the following co

Re: Platform mismatch error

Hello macports, Still the same error: As the subject says, Platform mismatch error. Some details: Sonoma 14.6.1 on M1 Max 64Gb. I reinstalled completely macports after removing all. And I get the same error. What to do in this case? I suspect you are running your terminal or shell through Rose

Re: Error upgrading to macport 10.0

hello, It is bizarre! Here is what I get: Error: Current platform "darwin 23" does not match expected platform "darwin 23" Error: Please run 'sudo port migrate' or follow the migration instructions:https://trac.macports.org/wiki/Migration OS platform mismatch while executing "mporti

Re: port outdated complains after self-update to version 2.10 of MacPorts

port outdated sqlite error: attempt to write a readonly database (8) while executing query: CREATE INDEX registry.snapshot_file_id ON snapshot_files(id) while executing "registry::open $db_path" (procedure "mportinit" line 832) invoked from within "mportinit ui_options global_option

MacPorts 2.10.0 has been released

The MacPorts Project is happy to announce that the 2.10.0 version has now been released. It is available via the usual methods: - selfupdate if you already have MacPorts installed - package installers [1] for macOS 14 Sonoma and all older releases back to Mac OS X 10.5 Leopard (un

MacPorts 2.10.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.10.0-rc1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) If no s

MacPorts 2.10.0-beta2 now available for testing

Source code and pkgs for MacPorts 2.10.0-beta2 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) There

Re: MacPorts 2.10.0-beta1 now available for testing

Nils Breunese wrote: Bill Cole https://lists.macports.org/mailman/listinfo/macports-users>>: > The following ports were restored with changes: > - openjdk17-zulu > state changed from 'installed' to 'inactive' > - openjdk21-temurin > state changed from 'installed' to 'inactive' > In what circums

Re: MacPorts 2.10.0-beta1 now available for testing

Bill Cole wrote: Surprisingly few issues, and I like the way this spat out at the end so I didn't need to read the whole scrollback: ---> Note: Migration finished with errors. The following ports could not be restored: - clang-12 Skipped becuase its dependency llvm-

MacPorts 2.10.0-beta1 now available for testing

Source code and pkgs for MacPorts 2.10.0-beta1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) There

Re: py-numpy 2.0.0

>/Would introducing a py-numpy2 port be a possible solution? />//>/Nils. / Unfortunately, that’s not how python packages work. They need to install into the same directory spaces as to be available for other packages, e.g. /opt/local/Library/Frameworks/Python.framework/Versions/3.12/lib/python

Re: Call for testing: port migrate

. Will let you know the outcome… Ciao Franco On 12 Jun 2024, at 09:00, Joshua Root wrote: A 'migrate' action has been added to MacPorts base in git on the master branch. If you are comfortable with checking out the git repo, installing MacPorts from source, running potentially

Call for testing: port migrate

A 'migrate' action has been added to MacPorts base in git on the master branch. If you are comfortable with checking out the git repo, installing MacPorts from source, running potentially buggy pre-release code, and reporting any issues, we would greatly appreciate you giving it a try. The ne

Re: xcode not found while building

Ryan Schmidt wrote: On May 26, 2024, at 14:33, Riccardo Mottola wrote: > > Hi, > > MacVim is difficult to build, I want to get a version build on older versions of MacOS. > I am trying to get a version building on 10.11. The current versions and most previous versions don't build, because X

Re: Macports, pip, and vent

I’m setting up to use a collection of python codes developed by someone else, and to run them I’ll need to use some python modules/packages that aren’t available via MacPorts (nvector, pykml, and stripy). From looking over old posts it appears that the best way to do this is to install all of

Re: what MacPorts port would create a TAGS file (looks like a history helper, rlwrap?)

what MacPorts port would create a TAGS file (looks like a history helper, rlwrap?) https://www.gnu.org/software/emacs/manual/html_node/emacs/Tags-Tables.html

Re: force rebuild a port

Richard L. Hamilton wrote: A URL likehttps://ports.macports.org/port/harfbuzz/builds/ in your browser (but put in the port name you want in place of harfbuzz) will show what if anything is pre-built for that port. Other views are available,

Re: MacPorts 2.9.3 has been released

Dave Horsfall wrote: I hadn't got around to installing 2.9.2 yet (I do those admin tasks on Mondays); will 2.9.3 drop cleanly onto 2.9.1? I ask because I got bitten by a Linux upgrade; apparently Debian (if not all of them) requires all intermediate upgrades be performed... We aim for direct

Re: MacPorts 2.9.3 has been released

On 4/4/2024 15:29, Peter West wrote: I’ve installed 2.9.3. As with 2.9.2, port selfupdate did not update the port install. Is this something you’re aware of? It always takes a little time for releases to propagate to the rsync mirrors. 2.9.2 took longer than usual because of some downtime for

MacPorts 2.9.3 has been released

The MacPorts Project is pleased to announce the release of version 2.9.3. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new inst

MacPorts 2.9.2 has been released

The MacPorts Project is pleased to announce the release of version 2.9.2. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new insta

Re: Library libtdbc used in restore_ports script is unsigned

On 21/3/2024 23:33, Eric Gallager wrote: On Thu, Mar 21, 2024 at 12:53 AM Joshua Root wrote: Hopefully we can ship automatic migration in MacPorts base soon and retire restore_ports.tcl. Yeah, please notify me once this happens; I've been reluctant to update from Big Sur just due t

Re: Library libtdbc used in restore_ports script is unsigned

I recently upgraded from macOS 13.x to macOS 14.3.1 Sonoma and started running the MacPorts Migration process. I got interrupted and did the minor macOS update to macOS 14.4 and tried to run the “restore_ports.tcl” script, which worked for a while but then threw an error about the libtdbc libra

Re: MacPorts vs. Apple compiler issues, Handle

(Moving to macports-dev as it is a better fit for this topic.) On 18/3/2024 22:50, Riccardo Mottola wrote: I will do another compilation reducing the optimization level. GCC has an issue where beyond gcc6 certain optimizations need to be disabled, or AF crashes. Issues that only appear at hig

Re: ld: can't write output file for architecture ppc

raf wrote: I've been told that macports needs to be selfupdated at least annually. If it's been too long between selfupdates, it can fail (It did for me once on 10.6.8). You might need to reinstall macports instead of selfupdate. To any expoerts out there, does that sound helpful? I wouldn't

Re: MacPorts vs. Apple compiler issues, Handle

On 13/3/2024 20:52, Riccardo Mottola wrote: I found a minor patch by Firefox to solve this namespace collision. So for whatever reason Apple's did differently, it now compiles on all compilers. However clang9 generates a crashing executable. I tried on both 10.11 and 10.13. - Apple clang: w

Re: MacPorts vs. Apple compiler issues, Handle

MacPort installs: $ clang-mp-9.0 --version clang version 9.0.1 Apple: $ clang --version Apple LLVM version 9.1.0 (clang-902.0.39.1) Is there some Apple "trick" or is it the slight compiler difference in version? The version difference is less slight than you might think. Apple clang version n

Re: is there a Fortran-90 compiler port? Where to get a FOSS Fortran-90 compiler?

Yes. Or as Eric suggested, you can use 'port select' to create a 'gfortran' link. - Josh On 2/3/2024 15:35, Kenneth Wolcott wrote: Should I be using gfortran-mp-13? ls /opt/local/bin | grep fortran arm64-apple-darwin23-gfortran-mp-12 arm64-apple-darwin23-gfortran-mp-13 gfortran-mp-12 gfortran

Re: is there a Fortran-90 compiler port? Where to get a FOSS Fortran-90 compiler?

Are you sure of that? Check e.g. 'port contents gcc13 | grep gfortran'. - Josh Kenneth Wolcott wrote: Hi Noam; I do not have gfortran, therefore I must not have gcc? Here is a filtered list of the ports that I have installed that pertain to gcc: gcc12 @12.3.0_4+stdlib_flag (active)

Re: Port reclaim unexpectedly wants to uninstall a subport, when the top level port is installed

I'm puzzling over some weird "port reclaim" behaviour on one machine. On the problematic machine, I installed py-matplotlib, which correctly installed py312-matplotlib. But, if I run "port reclaim", it wants to uninstall py312-matplotlib as a "Unrequested ports without requested dependents fo

MacPorts 2.9.1 has been released

The MacPorts Project is pleased to announce the release of version 2.9.1. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new instal

MacPorts 2.9.0 has been released

The MacPorts Project is happy to announce that the 2.9.0 version has now been released. It is available via the usual methods: - selfupdate if you already have MacPorts installed - package installers [1] for macOS 14 Sonoma and all older releases back to Mac OS X 10.4 Tiger (universal

Re: /opt/local/var/macports

Are there negative side-effects to moving this largish subdirectory to an external drive and connecting via soft link? I haven't tried it myself in a while, but as far as I know having it on another volume should work fine. You don't need the link, since this location is configurable as 'port

MacPorts 2.9.0-rc2 now available for testing

Source code and pkgs for MacPorts 2.9.0-rc2 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) If no sh

MacPorts 2.9.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.9.0-rc1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) If no sh

  1   2   3   4   >