Re: sunclock

> I recently upgraded a macbook air from 10.6 to 10.13 > and discovered that sunclock is no longer in macports. > > Does anyone know which was the last version of macos > whose corresponding macports included sunclock? That isn't how MacPorts releases work. There is one set of Portfiles that are

Re: port install tuntaposx fails - Mac OS MOJAVE

Unfortunately tuntaposx has not had an upstream release since 2015, and currently has no maintainer in MacPorts. - Josh

Re: conflicting variants while rebuilding a dependency

Riccardo Mottola wrote: > I get this (Lion 10.7): > > --> Scanning binaries for linking errors > Could not open /opt/local/lib/libexiv2.26.dylib: Error opening or > reading file (referenced from /opt/local/lib/libgexiv2.2.dylib) > ---> Found 1 broken file, matching files to ports > ---> Found

Re: conflicting variants while rebuilding a dependency

On 2019-1-14 09:59 , Riccardo Mottola wrote: > Hi Joshua, > > On 2019-01-13 02:04:30 +0100 Joshua Root wrote: > >> >>> The following ports are currently installed: >>>     gexiv2 @0.10.8_1+python27+python36 (active) >> >>> So, I suppose

Re: How To Troubleshoot MacPorts

Michael Newman wrote: >> On Apr 12, 2019, at 06:19, Ryan Schmidt wrote: >> >> It's difficult to answer a question this broad. But I can tell you a little >> about how I answer port build failure bug reports or posts on the list. > > Thank you for taking the time to write such an interesting and

Re: "Fetching archive" fails for all ports on multiple systems, different networks

Lee Finn wrote: > Hi Dave et al. > > I repeated the curl. The md5 checks: the xfer was completed correctly. Which curl was it though, MacPorts or system? (Running 'type curl' will answer this.) > Advice welcome! I would check if you have any proxies configured, via any of System Preferences, en

Re: "Fetching archive" fails for all ports on multiple systems, different networks

On 2019-4-14 15:17 , Lee Finn wrote: > Hi Joshua,  > > The curl is the MacPorts curl. The linking is the same as your reference.  OK, so do you get the same result with /usr/bin/curl? - Josh signature.asc Description: OpenPGP digital signature

Re: Wireshark, Qt5 and El Capitan

On 2019-4-21 14:23 , Chris Jones wrote: > Hi, > > I was curious, so I fired off a build using the buildbots, just to see > what would happen in a clean environment. > > https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/84721/steps/install-dependencies/logs/stdio > > And indee

Re: Wireshark, Qt5 and El Capitan

On 2019-4-21 15:37 , Christopher Jones wrote: > Hi, > > Just to finish up, as the fix seemed trivial (us the PG to set the deps) > I have pushed an update doing just this. So update and try again. This port is not openmaintainer; please don't make changes without maintainer permission or a timed-

Re: Wireshark, Qt5 and El Capitan

On 2019-4-21 21:19 , Chris Jones wrote: > > >> On 21 Apr 2019, at 10:45 am, Joshua Root wrote: >> >>> On 2019-4-21 15:37 , Christopher Jones wrote: >>> Hi, >>> >>> Just to finish up, as the fix seemed trivial (us the PG to set the deps) >

no destroot found (was: help please)

> what does this mean … > > [haycorn] /Users/jam/DEVEL [580]% sudo port install qt511-qtwebkit > ---> Computing dependencies for qt511-qtwebkit > ---> Installing qt511-qtxmlpatterns @5.11.3_0 > Error: Failed to install qt511-qtxmlpatterns: no destroot found at: > /opt/local/var/macports/build/_

Re: OpenBLAS binary packages

> I am trying to understand why I am not able to get the OpenBLAS port to > install exclusively from binary packages, i.e. using something like: > sudo port -b install OpenBLAS > Even if I prepare a local repository with the prebuilt binary packages it > indicates that it is not able to find an

Re: OpenBLAS binary packages

Chris Jones wrote: > Its not possible to get binary installs for OpenBLAS due to license > conflicts between it and one of its deps, openssl IIRC. Because of this > the buildbots flag the builds as non-distributable. That's often the reason why binary packages are not available, but not in this

Re: OpenBLAS binary packages

On 2019-5-15 19:01 , Artur Szostak wrote: > OK, I must be blind. Thanks for indicating archive_sites. I completely missed > that when looking at the Portfile yesterday. This explains everything. > > This raises the question: how is the MacPorts team mitigating the cost of > compiling OpenBLAS ov

Re: output like "port list all" over the web?

Richard L. Hamilton wrote: >> On Aug 4, 2019, at 23:53, Dave Allured - NOAA Affiliate via macports-users >> wrote: >> >> So will it be sufficient to simply run "port list all" on the current stable >> MacPorts package, as a frequent automatic process? Capture the text result >> and put it in

New MacPorts ports database site

MacPorts' new ports database is live at . Please consider installing the "mpstats" port to enable submission of anonymous information about your system and installed ports for statistical purposes. The information collected is currently: * MacPorts version * OS name an

Re: Why does everything now want ncurses-bootstrap, which doesn't build???

Bill Cole wrote: > So it's that time of the month: time for a port > {reclaim,selfupdate,upgrade outdated} cycle on my Snow Leopard machine, > which has a stable working "LibcxxOnOlderSystems" setup. > > Or at least, it HAD a stable working "LibcxxOnOlderSystems" setup. Now, > upgrades are broke

Re: Why does everything now want ncurses-bootstrap, which doesn't build???

> On 23 Aug 2019, at 21:00, Joshua Root wrote: > >> The reason for the *-bootstrap ports is that 10.6 doesn't come with >> libc++. So you need to be able to build a compiler capable of building >> libc++, while only using the system's libstdc++. That compiler is

Re: LibcxxOnOlderSystems

On 2019-8-29 20:04 , Bjarne D Mathiesen wrote: > > > Ken Cunningham wrote: >>> --- >>> Now, how do I switch this automatic process off ? >>> I really need to get my system into a working condition ;-) >>> >> I think if you start over, uninstall all ports, and then set your >> macports.conf back

Re: LibcxxOnOlderSystems

On 2019-8-29 21:21 , Bjarne D Mathiesen wrote: > > #=> port deps clang-3.4 > Full Name: clang-3.4 @3.4.2_12+analyzer > Build Dependencies: cctools > Library Dependencies: libxml2, llvm-3.4, python27, libffi, ncurses, zlib > Runtime Dependencies: clang_select, ld64, perl5 I guess you don't have

Re: LibcxxOnOlderSystems

On 2019-8-30 00:53 , Bjarne D Mathiesen wrote: > I > 1) uninstalled all installed ports > 2) manually cleared the build directory for cruft What about variants.conf? > So ... 👎🏻 it fails already after the first port has been installed 👎🏻 Yeah, there's no getting around the fact that +llvm37 isn'

MacPorts 2.6.0-beta1 now available for testing

Source code and pkgs for MacPorts 2.6.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 a

Re: OpenCL deprecation in MacOS 10.14

vincent habchi wrote: > Folks, > > I’m currently upgrading the GDAL port to 3.0.1 and… the OpenCL code doesn’t > work anymore. No way I can find the file OpenCL.h anywhere in the system. I > suppose this is part of Apple policy of deprecating OpenCL, so that no one > can build new software base

MacPorts 2.6.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.6.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 sho

MacPorts 2.6.0 has been released

The MacPorts Project is happy to announce that the 2.6.0 version has now been released. It is available via the usual methods: - selfupdate if you already have MacPorts installed - package installers for 10.14 [1], 10.13 [2], 10.12 [3], 10.11 [4], 10.10 [5], 10.9 [6], 10.8 [7], 10.7 [8], 10.6

Re: Problems with MP 2.6.0 on Snow Leopard

Hi Rob, Rob Widdicombe wrote: > I'm still resolutely running Snow Leopard and last night did a port > selfupdate to take me up to MP 2.6.0. So far so good. > > However, when I then tried to do a port rev-upgrade, the problems began. It > fails on the first step, upgrading gmp. Looking at the lo

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

(forgot to include the list on first sending, apologies for duplicate message) Chris Jones wrote: > Indeed, gcc8 is not supported on 10.5 or older, and likely will never be. > > What is requiring you to use libgcc8 ? libgcc7, apparently: % port deps libgcc7 Full Name: libgcc7 @7.4.0_3 Extract D

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

On 2019-9-25 18:31 , Riccardo Mottola wrote: > Hi, > > Joshua Root wrote: >> Chris Jones wrote: >>> Indeed, gcc8 is not supported on 10.5 or older, and likely will never >>> be. >>> >>> What is requiring you to use libgcc8 ? >> libgcc7, ap

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

On 2019-9-27 06:01 , Christopher Jones wrote: > Hi, > > From the output it appears cmake has a dependency on both libgcc and libgcc8. > This is not correct on 10.5. > > You should file a ticket against cmake to bring it to the attention of the > maintainer. It's not cmake doing it. The problem

Re: gnutls dependencies

Kastus Shchuka wrote: > gnutls was recently upgraded to 3.6.10_0. When I try to upgrade gnutls, it > pulls in a tall list of dependencies: > > ---> Computing dependencies for gnutls > The following dependencies will be installed: > clang-8.0 > clang_select > docbook-xml > docbook-xml-4.1.2

MacPorts 2.6.1 has been released

The MacPorts Project is pleased to announce the release of version 2.6.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 installs,

Re: snowleopardfixes is obsolete; please uninstall it.

Jeffrey Walton wrote: > I'm trying to get an old PowerMac upgraded. I'm seeing the error > message below. Cat'ing the log, I can't tell which package I should > remove. > > What package should be removed? > port upgrade outdated > ---> Configuring snowleopardfixes > Error: snowleopardfixes is

Re: sudo port selfupdate Doesn't Seem To Work

Michael Newman wrote: > What’s going on here? > > ---> Updating MacPorts base sources using rsync > MacPorts base version 2.5.4 installed, > MacPorts base version 2.6.1 downloaded. > ---> Updating the ports tree > ---> MacPorts base is outdated, installing new version 2.6.1 > Installing new Mac

Xcode 11 on Mojave (was: libSystem not found using gfortran)

Xcode itself only contains a 10.15 SDK, but the Command Line Tools have a 10.14 one. You should be mostly fine with them installed, though there are some exceptions. Our installation instructions have always said to install both Xcode and the CLTs. - Josh Chris Jones wrote: > yes, as it only has

Re: Xcode 11 on Mojave

On 2019-10-13 02:06 , Ryan Schmidt wrote: > > > On Oct 12, 2019, at 03:36, Chris Jones wrote: > >> On 12 Oct 2019, at 3:28 am, Ryan Schmidt wrote: >> >>> On Oct 11, 2019, at 09:57, Joshua Root wrote: >>> >>>> Xcode itself only contains a 1

All compilers are either blacklisted or unavailable (was: compiler warning)

Ryan Schmidt wrote: > On Oct 11, 2019, at 23:11, Andrew Hartung wrote: > >> On Oct 11, 2019, at 9:39 PM, Ryan Schmidt wrote: > >>> On Oct 10, 2019, at 22:58, Andrew Hartung wrote: >>> Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback opti

MacPorts 2.6.2 has been released

The MacPorts Project is pleased to announce the release of version 2.6.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 installs,

Re: Problem installing the grace port

> Dear Macports users, > > I have a MacBook Pro with MacOS 10.13.6 on which I installed several programs > through Macports. However, when I installed the grace package in order to use > plotting program xmgrace, the following message error pops up: > > Warning: Widget must be a VendorShell. >

Re: Problem installing the grace port

On 2019-11-17 04:54 , Ippoliti, Emiliano wrote: > Dear Joshua, > > thank you for your detailed answer. > In fact, looking at the content of my DYLD_LIBRARY_PATH variable: > >> echo $DYLD_LIBRARY_PATH > /usr/local/qt/lib:/usr/local/psh/lib:/usr/local/dt/lib:/usr/local/netpbm/lib:/opt/lib > > and

Re: Local ports repository for non-standard prefix

Raphael Cohn wrote: > Regardless, how do I go about creating a local file repo of binary ports? We have a how-to document on the wiki about this: It uses a web server, but it should be easy enough to adapt the instructions to use a file URL in

Re: Local ports repository for non-standard prefix

On 2020-1-15 21:52 , Raphael Cohn wrote: > Joshua, > > Thank you. > > I've followed that document, used a file URL and still got the error > described. I've triple-checked that the settings match. Well I just tried it here and it seems to be working. With MacPorts installed in /opt/mptest and thi

Re: Test in local repository without privileges

Dave Allured wrote: > Is there an easy way to get macports to go through the motions of "port > install -s" for a single port, using macports infrastructure, and taking > port dependencies from /opt/local, but writing only inside a user > directory? You can't install or activate without write acce

Re: Problems with not finding Framework header files on Mojave 10.14.6

Greg Earle wrote: > I have Xcode 10.3 installed on it (to ensure it installed the 10.14.6 > SDK). Xcode 11 should also be OK as long as you have the Command Line Tools installed, which will provide the 10.14 SDK. > Warning: The macOS 10.14 SDK does not appear to be installed. Ports may > not bu

Re: opensp fails to build

Uli Wienands wrote: > Trying to fix some (a lot of) broken ports. Running into a snag with > opensp, which fails to build. Fixed: > This is surprising as I must have had at some point a working install o

rsync server is down (and a workaround)

As you may have noticed, the server at FAU that hosts rsync.macports.org is currently down. There was a hardware failure, and work to restore service is in progress. If you need to selfupdate in the meantime, you can use a different mirror as described at .

Re: libffi

Curtis Matz wrote: > I’ve installed libffi but I’m trying to compile and it says it can’t find > ffi.h. How do I tell my compiler which happens to be gcc9 to look in > /opt/local for the header file? > >> port installed | grep libffi > libffi @3.2.1_0 (active) > > src/rtlib/thread_call.c:33:

Re: rsync and different UTF normalization in APFS vs HFS+

Ces VLC wrote: > On Sat, Jul 4, 2020 at 2:43 AM Jim DeLaHunt > wrote: >> >> [...] I hope you see the distinctions I'm trying to explain. And, I hope > this helps you figure out a solution. Please let the list know what you > find out. >> > > Thanks a lot, Ryan and Jim, for your messages and for t

MacPorts 2.6.3 has been released

The MacPorts Project is pleased to announce the release of version 2.6.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 installs,

Re: setting up apache2 (or squid) to serve as an SSL/TLS proxy for older systems?

Ken Cunningham wrote: > I have finally found and followed a webmin walkthrough on setting up squid on > Ubuntu that worked > > and thereby > sorted out how to use squid as

Re: com.apple.quarantine attribute on MacPorts files?

> Out of curiosity, looking for files that seemingly without good cause had the > com.apple.quarantine extended attribute on them, I noticed that almost all > (417 out of 425) of the files installed for port libsdl had it on them (as > well as two files for xephem: /opt/local/share/xephem/auxil

Re: apg still very useful, please don't deprecate

Sean DALY wrote: > So if it is possible to keep apg around, please do, I use it all the time > and it performs its job very well with no bugs I have ever encountered The danger is not that it will be removed just for being old, but that it will one day start failing to build with the latest develo

Re: apg still very useful, please don't deprecate

erated password verbatim). I > also keep an older Mac around offline to run deprecated software which > is still useful. What I like about apg today is I have it in any of my > terminals when I need it. > > thanks > > Sean > > On Sun, Aug 16, 2020 at 9:35 AM Joshua Root <m

Re: python2.7 throws bus error when issuing `help("modules")'

joerg van den hoff wrote: > seen with current macports and > > Python 2.7.18 (default, Apr 22 2020, 05:03:29) > [GCC 4.2.1 Compatible Apple LLVM 11.0.3 (clang-1103.0.32.29)] on darwin > > I get a reproducible bus error when trying to get a list of known modules > > with `help("modules"). > > /u

Re: python2.7 throws bus error when issuing `help("modules")'

On 2020-8-24 18:34 , joerg van den hoff wrote: > > thanks for this suggestion. I have had a look and cannot make sufficient > sense of it. here is the leading section with the traceback: > do you see the problem? I don't :| Well, I don't know why it's crashing, but it's crashing in _objc.so whi

Re: Apple ARM binary codesign issue

On 2020-9-23 05:33 , Ryan Schmidt wrote: > > Send feedback through the Feedback Assistant app. Yes, everyone with any issues with Apple preview software should do this early and often. I've read that number of duplicates is one of the ways they determine issue priority internally. - Josh

MacPorts 2.6.4 has been released

The MacPorts Project is pleased to announce the release of version 2.6.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 installs,

Re: MacPorts on Apple Silicon Macs (was: Re: info)

Ryan Schmidt wrote: > We have tens of thousands of ports in MacPorts and it's not always clear to > us which ones people use. That at least can be easily remedied by installing the mpstats port. You should still file a ticket if something is broken (and there isn't an existing ticket) of course.

Re: Migration doc suggestion - chsh

Ryan Schmidt wrote: > On Nov 27, 2020, at 15:50, Kevin Horton wrote: > >> I'm apparently a slow learner, but once again I forgot to change my login >> shell back to one supplied by Apple before migrating to Big Sur (I had been >> using. >> >> Suggestion - add a step to the Migration docs, befor

Re: Problem with eggbus on Intel machines

And what's more, it was deleted from the tree in 2013 - that's impressive persistence. :) Definitely safe to uninstall. You can find ports that are installed but no longer available in the ports tree with

Re: CLI Tool Problem

Tom wrote: > I get the following Error Message, although Xcode 12 and the CLI Tools are > installed: > >>> Warning: The macOS 11.0 SDK does not appear to be installed. Ports may not >>> build correctly. >>> Warning: You can install it as part of the Xcode Command Line Tools package >>> by runni

Re: restore_ports.tcl failure

Murray Eisenberg wrote: > I’m trying to migrate my ports, originally installed under Catalina > (actually, migrated from my iMac running Catalina), to Big Sur 11.1 on an M1 > MacBook Air. When I got to the step > > sudo ./restore_ports.tcl myports.txt > > I get the following error message: > >

Re: Apple Silicon and universal builds

Mark Bestley wrote: I have just got an Apple Silicon Mac Mini and am trying to install some ports I am trying to use just arm code. However some ports put a +universal variant as the default. This would not be a problem except some ports do not build if universal e.g. python38 and icu. Exampl

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

Re: SDK does not appear to be installed

Gary Palter wrote: The release notes for Xcode 12.4 state that it includes the 11.1 SDK. Apparently, there’s no version of Xcode with an 11.2 SDK. (Xcode 12.5 has the 11.3 SDK.) Right. At the time MacPorts 2.6.4 was released, it wasn't entirely clear how the SDK versions (and OS versions) we

Re: ARM gdb compilation fails with implicit function declaration error ioctl

Ryan Schmidt wrote: On Feb 23, 2021, at 15:44, James wrote: I looked, and looked at the forums how do I reply to list only? Press the Reply All button, then delete the recipients you don't want to send to. Or use a client that has a Reply to List function. - Josh

Re: Update on Big Sur Problems

Christopher Jones wrote: your basic issue is you are enabling by default the gcc5 variant, i.e. you get pmm:~ pet$ port variants atlas atlas has the variants: gcc49: build using macports-gcc-4.9 * conflicts with gcc5 mpclang37 perf [+]gcc5: build using macports-gcc-5 * conflicts with gcc4

MacPorts 2.7.0-beta1 now available for testing

Source code and pkgs for MacPorts 2.7.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: Scanning binaries segfault

Fielding, Eric J wrote: I was running a `port upgrade outdated` (actually I had to add `and not py37-scipy` as that was not building), and when it finished upgrading ports, it started the usual “Scanning binaries for linking errors”. This step is crashing with a “Segmentation fault” after abou

MacPorts 2.7.0-beta2 now available for testing

Source code and pkgs for MacPorts 2.7.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: Error: Failed to build source-highlight: command execution failed

I did as you suggested and after a lengthy period of time I got the following: Error: On macOS 10.7, libsdl2 @2.0.14 requires Xcode 4.3 or later but you have Xcode 4.2. Error: See https://guide.macports.org/chunked/installing.xcode.html for download links. Error: Failed to extract libsdl2: incomp

Re: clang: error: invalid version number in 'MACOSX_DEPLOYMENT_TARGET=11.3'

I’ve got a brand new MBP 16’’ from my employer and tried to use MacPorts on that. Since it is so new it sports macOS Big Sur 11.3 and Xcode 12.5 I know both are very recent and came out just a couple of days ago, so I am not expecting the impossible. Installing MacPorts itself went flawlessly

Re: MacPorts 2.7.0-beta2 now available for testing

On 2021-5-1 20:05 , Andrew Udvare wrote: Any chance this can get in to the final release? https://github.com/macports/macports-base/pull/225 Most likely not for 2.7.0. Typically only regression fixes are merged to the branch during the beta period. - Josh

MacPorts 2.7.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.7.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

MacPorts 2.7.0 has been released

The MacPorts Project is happy to announce that the 2.7.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 11 Big Sur and all older releases back to Mac OS X 10.4 Tiger (universal arm6

Note if you installed 2.7.0-rc1

There was one small fix that went in to the final release that was not in the release candidate. So you may want to ensure you have the final release by either running the package installer, or 'sudo port -f selfupdate', or installing from source manually. - Josh

Re: 'doctor' script

So: Is there a command (or a simple shell invocation) to walk over all packages to check whether all dependencies are fulfilled? I suppose that `sudo port upgrade outdated` doesn't do this for efficiency. Upgrading a port will first install any missing dependencies, so 'sudo port upgrade insta

Help wanted from Mojave users

Could someone with a 10.14 system running an Xcode version that defaults to building against the 10.15 SDK please try installing the tip of the release-2.7 branch on top of a MacPorts 2.6.4 installation? Report the results in the comments here: A specul

Re: macports << I run Mojave and can test that build

On 2021-5-24 00:04 , Jeffrey Jay Hayes wrote: Hi Joshua I have Xcode 11.3.1 installed .. I will have to check which version of the SDK is installed The definitive test is whether you get the SQL error shown in the ticket after selfupdating to 2.7.0 from an earlier version. You can check the

MacPorts 2.7.1 has been released

The MacPorts Project is pleased to announce the release of version 2.7.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 installs

Re: zathura install but fails with libjson.5.dylib not found

Uli Wienands wrote: I got zathura to install (and it rebuilt even through it seem like there should have been a binary). Then got the pdf -poppler plugin needed to actually decode pdf files. My problem is that zathura does not start up but bombs with libjson-c.5 not found. Her is the error me

Re: Running MacPorts on macOS 12?

First of all, please be aware of . Sorry for bugging the mailing list with a day-one beta. Trying to run macports with 'sudo port’ errors out with a OS platform mismatch error. Error: Current platform "darwin 21" does not match expected platform

Re: Does MacPorts need ALL of Xcode?

Ryan Schmidt wrote: Ports that include the xcode portgroup also most probably require Xcode. I would have thought that the xcode 1.0 portgroup would declare "use_xcode yes" somewhere in it, but it doesn't seem to. Maybe that is an oversight. It isn't. Setting build.type to "xcode" also sets u

Re: What is up with perl5.26 on Snow Leo?

Ulrich Wienands wrote: The funny thing is that almost every Macports install seems to want to upgrade this perl5.26; although as far as I can tell my perl5.26 is perfectly fine. So I am forced to use -n for each install to get anything done, which I fond a bit unsettling. Maybe I need to hose

Re: python ports depend on openssl not in index

SeaQuench wrote: After applying an update to MacOS last August, the python ports are reporting a dependency on either openssl11 or openssl3, neither of which are to be found in the (local?) index for MacPorts, according to the error I have received, copied below. While I am prompted to report

Re: [numpy @ bigsur: multithreading]

Maxim Abalenkov wrote: Dear all, I’m looking for guidance please. I would like to make sure, that I use all eight of my CPU cores, when I run Python’s 3.9.9 NumPy on my macOS BigSur 12.1. When I run my NumPy code, I see in ‘htop’, that only one ‘python’ process is running and the core utilis

Re: Building Ruby gems with MacPorts Ruby

It appears that the ruby31 port is missing something, as I can install ruby30, switch to it with sudo port select --set ruby ruby30, then install gems no problem. I just had a look and ruby31 is indeed doing something wrong. Here's the ticket I filed:

Re: Installation location for python code, tools, etc.

I'm not very experienced with Python, yet, but with regard to MacPorts, I'm trying to understand why when I do a pip3 install, or a direct install from a project tree ie: "python setup.py install" the tool(s) end up in this directory instead of /opt/local/bin|sbin etc: /opt/local/Library/Framewor

Re: port upgrade outdated hangs networking

This is extraordinary .. it presumably is a bug in MacOS. Running MacOS 10.15.7  on MacBook Pro 2016 I am updating various already installed packges in the usual way: sudo port upgrade outdated Everything goes along fine until the software reached gd2. I then see: --->  Fetching archive for gd

Re: What have I forgotten about specifying which Perl should be /opt/local/bin/perl?

Richard L. Hamilton wrote: >/On Jan 22, 2022, at 11:13, Ryan Schmidt > wrote: />//>/Release date information is not available in MacPorts. Are you proposing that the maintainer of every port should do research to discover the release

Re: Is this git handling of a problem on my macports-ports fork&clone OK?

Our suggested method of updating a fork is here: Hopefully you're not committing to master locally, as that's just asking for trouble. If you're not, no resetting or force pushing of master should be necessary. If you have uncommit

Re: Understaning rleaves, rdepof

Gerben Wierda wrote: So, how would you go about finding the ports on which what is actually installed depends? E.g.: if I have dovecot+solr8 installed, how would I find out which ports dovecot truly depends on on my system? Is there a reason that information is required apart from curiosity

Re: Is this git handling of a problem on my macports-ports fork&clone OK?

On 2022-2-21 10:01 , Gerben Wierda wrote: Stuff like ‘—autostash' and ‘popping the stash’ is gobbledygook to me. git is just something that covers so many complex scenario’s and I am using it so little in those scenarios that most of it is simply out of my understanding.

Re: Is this git handling of a problem on my macports-ports fork&clone OK?

On 2022-2-21 10:12 , Gerben Wierda wrote: The time I did a successful pull request, I think I did not first merge my working branch back into my own master, but I did a pull request from my branch from the GitHub website (after having pushed my branch to my own fork) It seemed to me, using my

Re: Is this git handling of a problem on my macports-ports fork&clone OK?

Gerben Wierda wrote: But I have been advised a pull is not enough, I should first do a fetch. If you're referring to my private reply, what I said was that a rebase was not enough to bring master up to date with upstream/master, you have to fetch as well. As per the git-pull man page:    

MacPorts 2.7.2 has been released

The MacPorts Project is pleased to announce the release of version 2.7.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 install

Re: Remove "Phantom" Ports

James Secan wrote: I have a number of apparently old/replaced ports (p5.26-*) that have been replaced at some point by their p5.28-* updates that are still in some way “alive” on my system. They show up when I run "port upgrade installed -u outdated” as follows: Warning: No port p5.26-

Re: port diagnose and xcode

I truly appreciate everyone who maintains things for MP - couldn’t live without this stuff. My initial query was just trying to understand whether ‘port diagnose’ was telling me something I should be concerned about. I think the answer was ‘no’. The message could be improved for that case, ce

Re: Corrupted ports.tar file?

Bill Cole wrote: Theory: it's a problem related to running the reclaim from the prompt at the tail end of a selfupdate. Incomplete 'portindex' run perhaps? Good theory. It's likely that when the periodic reclaim run at exit was added, it wasn't considered that it might be running after code

Re: zsh problems MacOS High Sierra

Ryan Schmidt wrote: On May 2, 2022, at 23:49, Sriranga Veeraraghavan wrote: >/I am not a zsh user, but according to zsh's documentation, ~/.zprofile is run only when zsh is used as a login shell, whereas ~/.zshenv is read for nearly every instance of zsh (including scripts): />//>/https://zsh

Re: Warning: Configuration logfiles contain indications of -Wimplicit-function-declaration; check that features were not accidentally disabled:

We have a wiki page with an in-depth explanation of what this warning means: The executive summary for end users is that this is something that the port's maintainer needs to look into, so you can file a ticket about it, but it may

<    1   2   3   4   >