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:

Re: [OT] bad disk & MacOS reinstall

On May 18, 2024, at 01:46, Richard L. Hamilton wrote: > > dyld[16578]: Symbol not found: (_gtk_plug_construct) > Referenced from: '/opt/local/lib/libgtkmm-3.0.1.dylib' > Expected in: '/opt/local/lib/libgtk-3.0.dylib' > Abort Are you using the quartz variant? This error was mentioned before

Re: Dovecot install Error

On May 18, 2024, at 00:21, Horst Simon wrote: > > Could not open /opt/local/lib/mysql8/mysql/libmysqlclient.24.dylib: Error > opening or reading file (referenced from > /opt/local/lib/dovecot/libdovecot-sql.0.dylib) This is https://trac.macports.org/ticket/70001

Re: [OT] bad disk & MacOS reinstall

On May 17, 2024, at 17:57, Riccardo Mottola wrote: > > Does Macports have a tool to get SMART details? The one that occurs to me is: https://ports.macports.org/port/smartmontools

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: Port Question and Suggestion

On May 14, 2024, at 15:19, Frederick Weinhaus wrote: > > Question: I have a question about which port to install when there are > several ports related to the name. What is the difference between portname, > py-portname, and py312-portname? Which should be installed? > > For example: tiff,

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

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 configuration and installation

Re: Preventing other software from linking against MacPorts libraries

On May 10, 2024, at 09:57, Smith wrote: > > Thanks all for the replies. The software depends on openssl, libpng and > libjpeg. And the name and version of the software that depends on those? > In the past with other projects I left MacPorts in place but used Homebrew to > install these

Re: Preventing other software from linking against MacPorts libraries

On May 9, 2024, at 01:03, Smith wrote: > > I occasionally run into a problem where I'm building software from a tarball > or a git clone outside of MacPorts, and the build process somehow ends up > linking or trying to link against libraries in the MacPorts space > (/opt/local). How can I

Re: where is the MacPorts gcc?

On May 3, 2024, at 23:12, Kenneth Wolcott wrote: > > I want to compile some C code using gcc to compare against clang. > > This code I want to compile needs gsl/gsl_vector.h so I used -lgsl to > compile with clang and it complained at runtime: "dyld[16321]: missing > symbol called". Since using

Re: where is the MacPorts gcc?

On May 4, 2024, at 02:06, Eric Gallager wrote: > > `ar` and `nm` are wrappers around the corresponding tools from > binutils/cctools; ar manipulates archives. nm shows you what symbols are in an object file. More about that in their documentation:

Re: where is the MacPorts gcc?

On May 3, 2024, at 23:12, Kenneth Wolcott wrote: > > I think "mp" means multiple precision... The "mp" suffix in gcc file names means "MacPorts". This is anachronistic now but it made sense back when gcc was included in Xcode. We wanted the executable "gcc-4.2" to mean Apple's fork of gcc-4.2

Re: Many "permission denied" errors.

On Apr 22, 2024, at 10:14, Carl Witthoft wrote: > > sudo port -f activate xorg-xorgproto > error message is > Warning: Failed to execute portfile from registry for xorg-xorgproto @2024.1_0 > ---> Activating xorg-xorgproto @2024.1_0 > Error: port activate failed: mkdtemp failed: Permission

Re: Fetching port getmail fails

On Apr 19, 2024, at 18:24, Horst Simon wrote: > > What I tried to explain is that the curl I used in previous installs was from > MacPorts, but when it failed I had only the macOS High Sierra native curl. That's what I thought you meant, but I don't think you've achieved that. You wrote: >

Re: Fetching port getmail fails

On Apr 19, 2024, at 17:17, Horst Simon wrote: > Yes, this was the problem, it used the macOS High Sierra curl, after adding > changing > the root profile using /usr/local/bin and /usr/local/sbin it worked ok. I'm not sure what you're referring to with the root profile. But after writing my

Re: Fetching port getmail fails

On Apr 19, 2024, at 00:15, contextnerror wrote: > > The issue is that you’re getting too many redirects for the pyropus.ca url. > I'm not sure why this is happening to you and not me. You probably use different versions of macOS and therefore different versions of curl. This is a bug in curl

Re: Poppler Build Error

On Apr 17, 2024, at 06:45, Curtis Matz wrote: > > I’m haven’t an issue compiling poppler. Has anyone else seen this issue? > > :info:build Traceback (most recent call last): > :info:build File "/opt/local/bin/g-ir-scanner", line 99, in > :info:build from giscanner.utils import dll_dirs

Re: build of rspamd and amavisd-new not working with High Sierra

On Apr 11, 2024, at 09:04, Bill Cole wrote: > > I got to > https://github.com/DCIT/perl-CryptX/pull/99/commits/9568b3e7ce17d9e3ace6ddbfb7df2d2e387aa91f > which shows the patch graphically. If you are dedicated to actually using > the 'patch' utility with a patchfile, there should be a way to

Re: build of rspamd and amavisd-new not working with High Sierra

On Apr 10, 2024, at 22:59, Horst Simon wrote: > > I tried to install amavisd-new on macOS High Sierra but fails in the install > of the dependency p5.34-cryptx, after this I tried to change to rspamd, > but rspamd too fails to build. > > I already created request ticket for p5.34cryptx. My

Re: macports2.93 p5.34-cryptx build failed

On Apr 8, 2024, at 19:10, Horst Simon wrote: > > fails with building p5.34-cryptx. > > Macports version 2.93 > OS High Sierra Version 10.13.6 Presumably this is https://trac.macports.org/ticket/68470

Re: always have broken files at the end of a self-update

On Apr 9, 2024, at 19:13, Alexander Newman wrote: > > I have exactly the same problem, but with rygel as another affected build. > I've uninstalled rygel but left webkit2-gtk in place. I now just ignore the > rev-upgrade suggestion (n). It seems to be associated with gstreamer and > cmake

Re: always have broken files at the end of a self-update

On Apr 9, 2024, at 13:02, Kenneth Wolcott wrote: > > At the end of each self-update I get the following error message, in > spite of whether I respond with yes or no: > > > ---> Updating database of binaries > > ---> Scanning binaries for linking

Re: force rebuild a port

On Apr 5, 2024, at 12:35, Riccardo Mottola wrote: > > If I do > > port -n upgrade --force --no-rev-upgrade harfbuzz > > > it completes in a matter of seconds... and the ol' MacBook isn't that fast :) > > I see cleaning, uninstalling, cleaning, installing activating, cleaning... > but never

Re: xz 5.6.1 vulnerability; downgrade to 5.4.6

On Mar 29, 2024, at 20:10, Ryan Schmidt wrote: > > it's not yet clear if or when or how [the developers] will respond to this. The official response page from the original developer is now up and will be updated with more information soon: https://tukaani.org/xz-backdoor/

xz 5.6.1 vulnerability; downgrade to 5.4.6

Today a security issue was disclosed [1] in the xz package, which contains the xz program (used for example by MacPorts to decompress xz-compressed source code archives) and the liblzma library (used by many other programs). Versions 5.6.0 and 5.6.1 (to which the MacPorts port was updated a

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

On Mar 19, 2024, at 10:21, Andreas Falkenhahn wrote: > >> When you upgrade, MacPorts will only deactivate the old versions of >> ports (unless specifically told to immediately uninstall them). So you >> should be able to activate the older versions to get back to the state >> you were in

Re: libiconv build fail w/macOS 14.4 (darwin/23.4.0) arch arm

On Mar 13, 2024, at 02:07, Paul Kippes wrote: > > I'm > seeing a build error with libiconv Fixed; see https://trac.macports.org/ticket/69462

Re: DMD port

On Mar 11, 2024, at 14:25, Kenneth Wolcott wrote: > >> On Mon, Mar 11, 2024 at 11:50 AM P Padil wrote: >> >> The dmd port is still at version 2.088 while upstream is at 2.107.1. Any >> reason it is still stuck at this ancient version? Can it be updated? There's a ticket about that:

Re: I just wanted to upgrade my older MacPorts version

On Mar 10, 2024, at 05:48, Riccardo Mottola wrote: > > I suppose that since you got the repository in git, you just need to do a > "git pull" to upgrade it and subsequently "sudo port -v sync". You don't need to run "git pull" manually. "sudo port sync" runs it for you.

Re: I just wanted to upgrade my older MacPorts version

On Mar 8, 2024, at 06:58, xmartin wrote: > > In fact, the the problem seems to be the restrictive corporate network. I was > able to run what is said in: > https://trac.macports.org/wiki/howto/SyncingWithGit Ok great. > The “sudo port upgrade outdated” is running, but the question know is,

Re: I just wanted to upgrade my older MacPorts version

On Mar 8, 2024, at 03:18, xmartin wrote: > > 1) You are right. The directory /opt/local/var has always been part of > MacPorts. In fact, I had a backup of the older version and, obviously this > directory was still there… The only important difference is that now this > /var directory

Re: Building "poppler" failed

On Mar 10, 2024, at 23:08, Dave Horsfall wrote: > > High Sierra 10.13.6 on ancient MBP. > > Doing my weekly "port upgrade outdated", it went belly-up here: > > - > >---> Building poppler >Error: Failed to build poppler: command execution failed

Re: I just wanted to upgrade my older MacPorts version

On Mar 7, 2024, at 06:30, Martin wrote: > I was running an older MacPorts version on my High Sierra and wanted to > upgrade the version just installing the newest one > (MacPorts-2.9.1-10.13-HighSierra.pkg) existing for my iMac. I did it and and > it was made with getting no errors or

Re: mozjs102

On Mar 6, 2024, at 06:13, Gregory Dodwell wrote: > >  > Will there ever be a mozjs102 port for the Sonoma version of MacPorts 2.9.1? > > I can't install Glade without it. On the MacPorts bugs re mozjs102 page > there's a big red 'X' near the Sonoma version. > > Any plans for an update?

Re: How to request new ports?

On Feb 5, 2024, at 11:00, lars.sonchocky-helldorf wrote: > > How would I request a port of a software I need, e.g. what’s the right way to > do this? You can file a ticket in Trac, setting the Type field to Request. To resolve it, someone has to do the work of creating the Portfile. It could

Re: MacPorts 2.9.0 & Xcode 15 on Ventura

On Jan 26, 2024, at 23:29, Sriranga Veeraraghavan wrote: > > My primary Mac is currently running Venture (13.6.3) but I have held off on > upgrading to Xcode 15 because I recall reading that there were some issues > with MacPorts and the linker on Xcode 15. > > With the release of MacPorts

Re: Can't build "mpv"

On Dec 24, 2023, at 21:30, Dave Horsfall wrote: > > MacBook Pro (13-inch, Mid 2010), High Sierra 10.13.6. > > Dunno what it is so it must be a dependency of something, but it fails > with: > >:info:configure meson.build:1474:21: ERROR: Command >

Re: Quartz no longer launching when an X application is invoked

On Dec 3, 2023, at 18:28, Kevin Horton wrote: > > I find in ~/.zprofile > > # MacPorts Installer addition on 2020-12-29_at_06:08:54: adding an > appropriate DISPLAY variable for use with MacPorts. > export DISPLAY=:0 > # Finished adapting your DISPLAY environment variable for use with MacPorts.

Re: Quartz no longer launching when an X application is invoked

On Nov 30, 2023, at 16:01, Kenneth Wolcott wrote: > > 3. My DISPLAY environment variable is set to ":0"; > I do not know where this variable is not being set properly or is > being overridden. You need to figure out where DISPLAY=:0 is being set, and remove the code that does so. It's probably

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 configure the

Re: Unistalling gmic-gimp macport

On Oct 11, 2023, at 06:23, Michal Sidorczyk wrote: > then I followed this instruction: > > > > https://guide.macports.org/chunked/installing.macports.uninstalling.html > > > > to remove macports completely. However, /opt/local still contains data (I > assume it is all macports related)

Re: Unistalling gmic-gimp macport

On Oct 11, 2023, at 02:03, Henning Hraban Ramm wrote: >  Am 11.10.23 um 07:34 schrieb Michal Sidorczyk: >> >> >> I know there are some upgrade instructions, but I did not follow them, I >> admit. Having the problem with disk space I do not put even more overhead of >> it, without being

Re: [unable to compile and link C++ code with g++ 12.3]

On Sep 20, 2023, at 11:57, Maxim Abalenkov wrote: > > I’m unable to run the ‘xcodebuild —version’. It complains: > > xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer > directory '/Library/Developer/CommandLineTools' is a command line tools > instance Use

Re: Timing of MacPorts Support for New macOS Versions

On Sep 21, 2023, at 00:26, Bryan Jones wrote: > > Dear MacPorts: > > I write to propose a policy change: a MacPorts release for a new macOS major > version should be publicly available by the time Apple publishes the final > Release Candidate version of macOS. > > Rationale: MacPorts is an

Re: checksum error on tree-sitter-go-mod

On Aug 5, 2023, at 15:17, ppadilcdx wrote: > > I always do a selfupdate before doing the ports' upgrades. Did a clean and > tried again just to make sure it wasn't corrupted on download. Not a clue how > to find out if it is a stealth update. I've filed a bug report for you in which I've

Re: trufflehog checksum fail

On Aug 1, 2023, at 22:37, Frank Cusackwrote: > > 1. did the failed version (3.45.3) of trufflehog actually have some error > with checksum? or is this a macports anomaly. A mistake was made when upgrading trufflehog to 3.45.3 on July 28: the maintainer forgot to update the checksums:

Re: Problem with binutils

On Aug 7, 2023, at 07:57, Maxim Abalenkov wrote: > > Hello Christoph, > > How are you? Have you tried to deactivate the ‘gdb’ first as the message > suggests? > > port deactivate gdb > > Then you may be able to install ‘binutils’ and activate the ‘gdb’ again. This is the bug report

Re: How to target older macOS version

On Aug 19, 2023, at 09:12, Andreas Falkenhahn wrote: > I've installed MacPorts on a macOS 13 system but I'd like to build programs > that run on all systems that have at least macOS 11. That's why I run gcc > with the -mmacosx-version-min=11.0 argument. This, however, leads to warnings > of the

Re: DDD 3.3.12 (arm-apple-darwin22.4.0) gets Xt error (installed from source via MacPorts)

On Apr 16, 2023, at 13:35, Kenneth Wolcott wrote: > Here's an email that I sent to the GNU ddd mailing list. I'll > forward the reply I received shortly. Looks like ddd and xQuartz are > not compatible? > > Thanks, > Ken Wolcott > > -- Forwarded message - > From: Kenneth

Re: port install hyper as a binary fails due to lack of arm64 variant (M1 chip)

On Apr 14, 2023, at 23:01, Kenneth Wolcott wrote: > port install hyper (build from source) fails (see bug #67241) I see the maintainer has not responded to the ticket. If you like, you could file a bug report with the developers and see if they have any suggestions for how to resolve this

Re: ports.tar owner/group

On May 7, 2023, at 19:42, Kastus Shchuka wrote: > After running port sync I see files extracted from ports.tar owned by a > non-existent group with numerical id 505: > > $ ls -l > /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ > total 474776 > -rw-r--r-- 1 root

Re: how to prepare an existing Macports instance for an xCode update or fix Macports after xCode update?

On Jun 2, 2023, at 13:53, Kenneth Wolcott wrote: > how to prepare an existing Macports instance for an xCode update or > fix Macports after xCode update? No preparation is needed. > I have an xCode update notification. > > I have an existing MacPorts installation. > > Do I need to do anything

Re: Portfile question for 10.6.8

On Jun 6, 2023, at 20:16, raf wrote: > That still leaves the question of how 10.6.8 hosts can download distfiles > from a non-https site (when https sites won't support TLS 1.0). Do distfiles > magically end up on http://distfiles.macports.org? Yes. Well, it's not magical, but it is automatic.

Re: mongodb 6.0 - No mongo or mongosh binaries

On Apr 7, 2023, at 07:02, Steven Green wrote: > After updating mongodb to version 6.0, there is no longer a mongo executable, > which is how you normally connect to it from a command line. > > The mongo web site says "The legacy mongo shell was deprecated in MongoDB 5.0 > and removed in

Re: argp.h

On Apr 7, 2023, at 04:23, Christoph Kukulies wrote: > Am 07.04.2023 um 11:02 schrieb Christoph Kukulies: > >> Anyone having an idea where the is buried? > > OK, I found in the macOS prerequisite list for macOS that the brew package > „argp_standalone“ is required. > I hate mixing brew and

Re: sudo port -v -s install solfege fails due to qtplay

On Mar 27, 2023, at 23:20, Kenneth Wolcott wrote: > > sudo port -v -s install solfege fails > > sudo port -v -s install solfege > Password: > ---> Computing dependencies for solfege..qtplay is known to fail. Try > to install anyway? [y/N]: n > Error: qtplay is known to fail > Error: Follow

Re: gv: dyld[77356]: symbol not found in flat namespace '_yylex'

On Mar 26, 2023, at 21:48, Kenneth Wolcott wrote: > > Running gv fails with dyld[77356]: symbol not found in flat namespace > '_yylex'. https://trac.macports.org/ticket/66211

Re: Nethack fails during patching on Ventura 13.2

On Feb 6, 2023, at 14:11, Jon Lasser wrote: > :info:patch File to patch: No file found--skip this patch? [y] 3 out of 3 > hunks ignored--saving rejects to Oops.rej This should have been fixed by: https://github.com/macports/macports-ports/commit/72e4024c311b6849e0bf3f2be320b8f9aa7a266a Run

Re: dia port (from source) fails to install on Ventura 13.1 (with M1 chip)

On Feb 5, 2023, at 13:46, Kenneth Wolcott wrote: > > The dia port (from source) fails to install on Ventura 13.1 (with M1 chip). > > The compressed install log file is attached. Thanks for adding your log to this ticket... https://trac.macports.org/ticket/66013 ...which is hopefully now

Re: poly2tri-c fails to install on Ventura 13.2 (with M1 chip)

On Feb 5, 2023, at 20:40, Alan Needleman wrote: > On Feb 5, 2023, at 8:30 PM, Ryan Schmidt wrote: >> Please run: >> >> sudo port clean poly2tri-c >> sudo port selfupdate >> >> Then try again. If it fails again, please attach the new main.log file to >

Re: poly2tri-c fails to install on Ventura 13.2 (with M1 chip)

On Feb 5, 2023, at 20:27, Alan Needleman wrote: > > On Feb 5, 2023, at 6:32 PM, Ryan Schmidt wrote: > >> On Feb 5, 2023, at 16:01, Alan Needleman wrote: >>> >>> I updated to Ventura 13.2 from Monterey 12..6.3 and migrated my Macports >>> installation.

Re: poly2tri-c fails to install on Ventura 13.2 (with M1 chip)

On Feb 5, 2023, at 16:01, Alan Needleman wrote: > > I updated to Ventura 13.2 from Monterey 12..6.3 and migrated my Macports > installation. All ports installed and seem to be working fine except for > poly2tri-c-0.1.0_0.darwin_22.arm64. It downloads and then gets to “installing > patches”

Re: mac and ssl/openssl

On Feb 5, 2023, at 16:08, Riccardo Mottola wrote: > Old versions of macs which I use, like 10.4 up to 10.7 have openssl and ssl.h > > I tested that 10.13 doesn't have, so GNUMail doesn't compile. > > Did Mac switch to a different ssl version and/or changed the location of it? > with which

Re: Getting errors when upgrading to Ventura

On Feb 5, 2023, at 16:25, Mannucci, Anthony J wrote: > I recently upgraded to Ventura and I am following the migration procedure. > > I updated Xcode etc. When restoring ports, I am getting errors associated > with perl and llvm. Should I file a bug report? > > Here is a list of error

Re: Install on Ventura 14.2

On Feb 2, 2023, at 20:58, Joshua Root wrote: > >> Putting together a new machine (M2Pro Mini, Ventura 14.2) and have hit a >> snag installing MacPorts. I’ve not installed Xcode on any of my systems for >> a number of years now, I simply install the appropriate CLI package from the >> Apple

Re: port install of xemacs fails due to failure to install Xaw3d

On Jan 31, 2023, at 01:21, Kenneth Wolcott wrote: > > I get a different error now when trying to install xemacs: > > *** PANIC *** Configure tests are not working - compiler is broken. > *** PANIC *** Please examine config.log for compilation errors. The preceding line was: :info:configure

Re: port install of xemacs fails due to failure to install Xaw3d

>> liblzma 5.2.7 >> >> On Sun, Nov 20, 2022 at 4:51 PM Ryan Schmidt wrote: >>> >>> On Nov 14, 2022, at 16:22, Kenneth Wolcott wrote: >>> >>>> This appears to be a common problem with several MacPorts install attempts. >>>> &g

Re: invoking evince generates a dbus warning regarding launchd; how to fix this?

On Nov 21, 2022, at 00:21, Kenneth Wolcott wrote: > invoking evince generates a dbus warning regarding launchd; how to fix this? > > dbus[28817]: Dynamic session lookup supported but failed: launchd did > not provide a socket path, verify that > org.freedesktop.dbus-session.plist is loaded! Run

Re: While trying to install lilypond, libuninameslist failed; install libuninameslist failed

On Nov 21, 2022, at 11:02, Kenneth Wolcott wrote: > > While trying to install lilypond, libuninameslist failed; install > libuninameslist failed > > Executing: cd >

Re: gv apparently silently fails to install properly

On Dec 19, 2022, at 15:55, Kenneth Wolcott wrote: > > I recently uninstalled and re-installed gv. > > There were no errors that I saw during the install (source code > build forced with "-s"). > > Yet, when I try to invoke gv, I get a what looks to be a linkage error: > > /opt/local/bin/gv

Re: Issue with installing port

On Jan 26, 2023, at 09:07, Will Senn wrote: > On 1/26/23 1:43 AM, Joshua Root wrote: >>> I'm trying to get pandoc to install. >> The ticket for this is , FWIW. > > I promise you I did search :). Thanks for the link though, it confirms it's > not just me!

Re: What is "ghc" and why was it installed?

On Jan 18, 2023, at 17:31, Clemens Lang wrote: > > On Wed, Jan 18, 2023 at 04:08:25AM +, Fielding, Eric J (US 329A) via > macports-users wrote: >> I was running “port selfupdate” and “port upgrade outdated” for the >> first time in a while, and I noticed that my Intel MacBook Pro was >>

Re: Macports won't uninstall

On Jan 23, 2023, at 12:43, Isabelle Dolan wrote: > I tried running uninstall and got this: > > Running command: /opt/local/bin/port -fp uninstall installed > > Error: No ports matched the given expression > > I am running a script that uninstalls macports using 'Running command: >

Re: Install/uninstall Direwolf program errors

On Jan 3, 2023, at 21:39, Larrie Deardurff wrote: > > I am running OS 13.1 on an intel iMac. I installed the program “Direwolf” > using Macports, following the intstruction listed here > (https://ports.macports.org/port/direwolf/). > > I was having some problems with Direwolf and realized

Re: ninja: build stopped: subcommand failed. Error: Failed to build gegl: command execution failed

On Jan 12, 2023, at 20:23, chilli.names...@gmail.com wrote: > What's strange is port outdated doesn't show anything, so I expect these > ports are broken and my install doesn't know it. I bet it has something to do > with port reclaim running when I tried to selfupdate. I deleted all the build

Re: How use py-pip?

On Nov 30, 2022, at 14:42, Murray Eisenberg wrote: > The python package I’m trying to install is pyobjc, for which no separte > MacPorts port seems to exist. PyObjC is available in the subports of the py-pyobjc port.

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

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. Apparently, the problem is that it cannot find a library: > > Crashed Thread:0 > > Exception Type:EXC_CRASH (SIGABRT) >

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

On Nov 11, 2022, at 13:34, Artemio González López wrote: > > I’m happy to report that after upgrading my ports —which took several days, > because for some reason gcc12 had to be compiled from scratch— Emacs now > works perfectly. You're on macOS 13 so everything will have to be compiled from

Re: port install of xemacs fails due to failure to install Xaw3d

On Nov 14, 2022, at 16:22, Kenneth Wolcott wrote: > This appears to be a common problem with several MacPorts install attempts. > > How do I install xemacs? > > excerpt... > ---> Extracting Xaw3d > ---> Extracting libXaw3d-1.6.4.tar.xz > Executing: cd >

Re: Where is port command documented?

On Nov 14, 2022, at 03:14, Lukas Oberhuber wrote: > > I was wondering where the port command flags are documented. For example, I'm > trying to uninstall a port in a script, but when two versions of the port are > installed, it interactively asks which I want to uninstall. > > The following

Re: how to move "Python Launcher" away from /Application folder?

On Nov 9, 2022, at 17:57, supervisitor wrote: > ... ups, this I have probably overlooked. (have made the installation from > source). > > But before I now uninstall everything to perform a reinstall, some further > questions: > > Can I do an installation with parameter

Re: Error installing Kampose

On Oct 28, 2022, at 12:23, James McManus wrote: > However, I am still not able to install Kompose. I'm still getting the not a > git repository error message: > > :info:build Executing: cd >

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

On Oct 29, 2022, at 07:50, Artemio González López wrote: > > Error: Failed to activate py310-jupyter: Image error: > /opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/__pycache__/jupyter.cpython-310.pyc > is being used by the active py310-jupyter_core

Re: Texmaker installation failed due to inability to build qt5 web engine

On Nov 4, 2022, at 07:03, Chris Jones wrote: > Just on this point, if you don't want to have to build everything from > source, then you should not update your OS before MacPorts has deployed > buildbots for the new OS. You can check this at e.g. > > https://build.macports.org/waterfall > >

Re: Libomp notes

On Nov 4, 2022, at 11:49, John Wiggins wrote: > I am running macOS Monterey 12.6.1 and updated Xcode and CLT to 14.1. > When I “upgrade outdate” I get note concerning libomp: > > … >> ---> Some of the ports you installed have notes: >> libomp has the following notes: >> To use this OpenMP

Re: iInstall denemo failed due to failure to configure qt5-qtbase

On Nov 1, 2022, at 17:46, Kenneth Wolcott wrote: > Very weird :-( > > xcode-select -p > /Library/Developer/CommandLineTools > > I can't find an Xocde.app on my machine *anywhere* :-( > > Guess I'll install yet again (SIGH*) > > Doesn't Xcode.app automatically get installed in the correct

Re: iInstall denemo failed due to failure to configure qt5-qtbase

On Oct 29, 2022, at 18:56, Kenneth Wolcott wrote: > > So I downloaded and installed the XCode RC 2 and CL Tools R2.. > > Then > > port diagnose > Error: The installed version of Xcode, none, is not supported by > MacPorts. For your currently installed system, the following versions > of Xcode

Re: Catelina xcode

On Oct 11, 2022, at 22:46, James Linder wrote: > My wife’s machine is Catelina (and Ends at Big Sur). It has, and I/She uses > lots of ports and IIRC we have used Qt before, but when I try to build > something I get the XCode license dialog. No worries, accept. "Something is > wrong see the

Re: Aubio fails to install as a prerequisite for Denemo

On Oct 27, 2022, at 12:01, Kenneth Wolcott wrote: > > I added a symlink: > > sudo ln -s /opt/local/bin/python3.10 /opt/local/bin/python > > The aubio app now installs successfully. Great, I'm glad that worked. That confirms that the port has a bug that needs to be fixed. Ports must not

Re: Permissions issue detected on the tarballs/base file during upgrade to MacPorts 2.8.0

On Oct 21, 2022, at 02:54, Olaf Sulla wrote: > Regarding the default UID and GID: > > - The GID, as you mention, already exists on the system via virtue of a > previous install of postgreSQL packages. > > - The UID 500 does not pre-exist. > > The latter might be the problem because

Re: Gnome aisleriot solitaire

On Oct 21, 2022, at 03:23, John Batistic wrote: > macOS Monterey > > I wish to install Gnome Aisleriot (and just realised that it is an anagram of > Solitaire) > But need assistance in making it happen. > > I have; > Successfully installed MacPorts, Gnome and Gnome Desktop, presuming that I >

Re: Permissions issue detected on the tarballs/base file during upgrade to MacPorts 2.8.0

On Oct 20, 2022, at 10:11, Olaf Sulla wrote: > I installed the update to MacPorts 2.8.0 earlier today on a Mac Mini A1 > running Monterey 12.6. > > During the install the following error was reported: > > NFO: Syncing port data and updating port-base ... > Password: > ---> Updating MacPorts

Re: Aubio fails to install as a prerequisite for Denemo

On Oct 16, 2022, at 20:28, Kenneth Wolcott wrote: > ---> Building aubio > Executing: cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_audio_aubio/aubio/work/aubio-0.4.9" > && /opt/local/bin/python2.7 ./waf build --verbose >

Re: dead man page links?

On Oct 1, 2022, at 01:39, Richard L. Hamilton wrote: > > Given a bunch of No such file or directory errors from man -k and/or > /usr/libexec/makewhatis, I looked a bit, and > > /opt/local/share/man/man1/dot2gxl.1 is provided by: graphviz > /opt/local/share/man/man1/fcat.1.gz is provided by: fsp

Re: Unable to build XV

On Sep 18, 2022, at 18:37, Dave Horsfall wrote: > >:info:build xvjp2k.c:77:5: error: redefinition of 'jas_getdbglevel' >:info:build int jas_getdbglevel(void) {return 0;} >:info:build ^ >:info:build /opt/local/include/jasper/jas_debug.h:123:5: note: previous > definition is

Re: Cannot build DOSBOX

On Sep 18, 2022, at 23:39, Dave Horsfall wrote: >---> Computing dependencies for dosbox >Error: Cannot install dosbox for the arch 'i386' because >Error: its dependency libsdl does not build for the required arch by > default >Error: and the configured universal_archs '' are not

Re: update

Please keep replies on the mailing list by using Reply All. On Sep 15, 2022, at 01:15, James wrote: > On 15 Sep 2022, at 12:30 pm, Ryan Schmidt wrote: > >> On Sep 12, 2022, at 16:56, James wrote: >>> >>> ... >>> checking for xcode-select... /usr/bin/

Re: libgcc9 and other ports that will never build on my system

On Sep 12, 2022, at 14:02, chilli.namesake wrote: > On Sep 12, 2022, at 11:49, Eric Gallager wrote: > >> On Mon, Sep 12, 2022 at 9:29 AM Bill Cole wrote: >> >>> Why are you trying to to build it for i386, e.g. 32-bit? Is there some >>> dependent that can't be built for x86_64? >> >> There are

Re: Monterey 12.6: cannot chown to _mysql for mysql datadir

On Sep 13, 2022, at 14:36, Murray Eisenberg wrote: > On 13 Sep2022, at 3:15 PM, Murray Eisenberg wrote: >> >> In the past, I’ve used the command >> >> chown +R _mysql:_mysql /Users/me/Databases/mysql/data >> >> as part of the steps to make a custom mysql datadir accessible to mysql. >>

  1   2   3   4   5   6   7   8   9   10   >