ClamAV: freshclam vs. sudo freshclam

If I run freshclam as a non-privileged user, it runs fine with no warnings or error messages. Here’s the last line of the response: Database updated (6622193 signatures) from db.TH.clamav.net (IP: 104.16.188.138) But, if I run sudo freshclam it fails with numerous

Mojave and Migration

I followed the migration instructions which are found here: https://trac.macports.org/wiki/Migration That sort of worked, except that some ports didn’t get reinstalled. For example, neither ImageMagick nor MPlayer were reinstalled. It was easy to

Re: Mojave and Migration

> On Oct 23, 2018, at 15:09, Ryan Schmidt wrote: >> Is there any way to find our without manually checking each and every port >> in myports.txt? > > Sure, get a list of only the port names you want to know about. For example > you could do that using: > > awk '{print $1}' myports.txt > >

Re: Mojave and Migration

> On Oct 23, 2018, at 16:17, Ryan Schmidt wrote: > > Were any of the ports in myports.txt, by chance, installed with the > +universal variant? If so, you'll have to install them without the +universal > variant on Mojave and later. Not by me. I’ve always installed ports with the simplest

Re: Mojave and Migration

> On Oct 23, 2018, at 15:31, Ryan Schmidt wrote: > >> Makes me thing something went seriously wrong with restore_ports.tcl. > > Ok, pick one, try to install it, see what happens. If it fails, show us what > the error was. Every one I’ve picked so far has installed without any errors. But,

Re: Mojave and Migration

> On Oct 23, 2018, at 19:48, Joshua Root wrote: > > Were there any failures shown in the output of restore_ports.tcl? Were > the missing ports mentioned at all? Running it again will not do any > harm since it will simply skip any ports in myports.txt that are already > active; what happens if

Re: Mojave and Migration

> On Oct 23, 2018, at 19:00,Chris Jones wrote: > > Do you create the requested list ? This is much shorter as it lists only > the ports your actively requested, not dependencies etc. My > recommendation is to go through this list, and just use it to identify, > by hand those you wish to

myports.txt vs requested.txt

I decided to compare the ports found in myports.txt with those in requested.txt. I figured that every port in requested.txt should also be in myports.txt. But, that’s not the case. Requested.txt contains only the following ports: ImageMagick clamav ffmpeg gstreamer010

Re: 10.14 Mojave

> Chris Jones wrote: > > MacPorts, for the most part, works fine on macOS10.14 now. Does that mean that I can install Mojave and that installed ports will continue to run without my having to install a newer MacPorts from source and perform a migration?

Re: Rust - Failed to Build

> On Mar 6, 2019, at 13:35, Ryan Schmidt wrote: > Rust is a programming language. The rust port provides a Rust compiler. You > need a Rust compiler if you want to compile software written in the Rust > language. > Now that the librsvg you use has been downgraded to a version that no

Rust - Failed to Build

I am aware that there is a bug report on this issue: https://trac.macports.org/ticket/57058 However, I have some different questions. This on a 2010 MBA running 10.9.5, Xcode 6.2 I first noticed this failure about six months ago. I chose to ignore it

Re: How To Troubleshoot MacPorts

> On Apr 12, 2019, at 23:50, Ryan Schmidt wrote: > > We explain some of this in our Guide, but I'll try to give an overview. Wow. That was incredibly helpful and very well done. You know how to write for people who don’t know as much as you do. That’s an uncommon skill in this field. You

Re: Upgrading MacOS From 10.9.5 To 10.13 - MacPorts Implications

On Jun 18, 2019, at 20:31, Ulrich Wienands wrote: > Hmm... per EveryMac.com , the 2009 MacBook Air only > goes up to 10.11. This agrees with my experience; my 2009 MBP also tops out > at 10.11. I’m sorry, it’s actually a late 2010 MBA. On June 10th the App Store

Upgrading MacOS From 10.9.5 To 10.13 - MacPorts Implications

I have an old 2009 MacBook Air (2GB RAM) which is running MacOS 10.9.5 (Mavericks). I’m now getting warnings from Apple, Google (Remote Desktop) and DropBox (among others) that this version of the OS will no longer be supported "real soon now". I have an installer for High Sierra (10.13) which

Re: Upgrading MacOS From 10.9.5 To 10.13 - MacPorts Implications

> On Jun 18, 2019, at 19:00, Chris Jones > wrote: > > Yes. You always have to follow the migration guide when updating to a > new major OS. Thanks. I have no problem with that. Done it many times in the past. But, there is still one thing I don’t fully

Migration Woes - Can’t Install Xcode Command Line Tools

This on a 2010 MBA that I only visit once a month. This visit I finally bit the bullet and upgraded from Mavericks to High Sierra. That upgrade wasn’t flawless, but it’s working. I also installed a compatible version of Xcode from the App Store. Now I’m stuck trying to install the command line

Re: Migration Woes - Can’t Install Xcode Command Line Tools

> `xcode-select --install` presents you with a dialog box through which you can > initiate either an installation of Xcode or an installation of the command > line tools. If you want to do both, initiate `xcode-select --install` a > second time after you've finished doing the first one. Thanks

Hoe To Troubleshoot MacPorts

I’ve been using MacPorts for many years now. While I understand the basics, I often run into problems that I cannot solve. Without exception, I have been able to post those problems here and get near-immediate solutions. For that I am grateful. On the other hand, I would ver much like to

Re: How To Troubleshoot MacPorts

> 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 informative post. I

Re: Problems With Mysql57

> On Jul 28, 2019, at 05:53, Ryan Schmidt wrote: > > Looking at the port select code, it just tries to create each symlink in > turn. There isn't any special error handling code to deal with the case that > a symlink can't be created; if that happens, an error will occur and MacPorts > will

Re: Problems With Mysql57

> On Jul 27, 2019, at 11:16, Ryan Schmidt wrote: > > `port select` is a convenience that places symlinks in /opt/local/bin. If > `port select` doesn't work, you won't be able to call the programs by their > convenient shortened names, but you can still call them by their absolute > paths

Problems With Mysql57

This was previously reported in March 2019, but nothing since then: https://lists.macports.org/pipermail/macports-users/2019-March/046514.html Here are the errors: mysql57-server has the following notes: If this

Re:Re: Problems With Mysql57

> On Jul 26, 2019, at 19:00, Christopher Chavez wrote: > > Not sure about your other issues, but the `port select` problem was > reported a while ago: > > https://trac.macports.org/ticket/58197 > Yes, I’m aware of that. But, I don’t understand the

Re: postgresql83-server - Further Woes

The only solution offered by the developer of DetectX was to tell DetectX to ignore changes to macports plist files. That seems to defeat the purpose of DetectX. DetectX is supposed to warn you of possible nefarious changes to your system. Choosing to ignore a possible problem is no

postgresql83-server - Further Woes

Periodically DetectX generates the following message: = Items: org.macports.postgresql83-server.plist Some background launch items have just been changed on your mac which can affect its security = I had previously uninstalled postgresql83-server and can’t find

Re: postgresql83-server - Further Woes

I have uninstalled the port, but DetectX keeps telling me that the plist has been changed. If it only happened once when I still had the port installed I’d say, yeah, problem solved. But when the plist keeps getting changed after the port has been uninstalled I have to wonder what’s happening.

Re: postgresql83-server - Further Woes

Thank you. Locate did not find this plist on the boot volume. It did find it in a Carbon Copy Cloner SafetyNet directory on a backup drive. MrMuscle:home mnewman$ locate org.macports.postgresql83-server.plist /Volumes/Clorox2/_CCC SafetyNet/2019-10-30 (October 30)

Re: mysql57, boost and postgresql84

Thanks Ryan. I have reactivated boost. The config log is here: https://pastebin.com/VdiZHn4k Mike > On Nov 6, 2019, at 12:30, Ryan Schmidt wrote: > > > > On Nov 5, 2019, at 19:39, Michael Newman wrote: > >> Maybe I’m just not smart enough to play with

mysql57, boost and postgresql84

Maybe I’m just not smart enough to play with MacPorts…. This on an iMac still running Mojave. This morning I did selfupdate and upgrade outdated with the following result: Error: mysql57 cannot be built while boost is active. Error: Please forcibly deactivate boost, e.g. by running: Error:

Re: mysql57, boost and postgresql84

I don’t know if it helps at all, but on October 24th I did the first steps of MacPorts migration in anticipation of installing Catalina. I never did install Catalina, but I saved the myports.txt and requested.txt files. They are here: https://pastebin.com/cxM85Dq6

Re: mysql57, boost and postgresql84

> On Nov 7, 2019, at 06:34, Ryan Schmidt > wrote: > > If `port installed requested` shows things that you don't actually want, tell > MacPorts by marking them as not requested: > > sudo port unsetrequested portname1 portname2 ... > >

Re: mysql57, boost and postgresql84

Thank you. I’m slowly (very slowly) beginning to pull all this together. > On Nov 7, 2019, at 06:34, Ryan Schmidt wrote: > > If `port installed requested` shows things that you don't actually want, tell > MacPorts by marking them as not requested: > > sudo port unsetrequested portname1

Re: mysql57, boost and postgresql84

On Nov 6, 2019, at 19:00, Chris Jones wrote: > You could also try rerunning > >> sudo port reclaim > > which does a number of tasks aimed at removing stuff you do not need. Thank you for that. It returned a massive list of unused and unneeded ports including this: > Found 1156 files (total

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

2 ---> Activating ffmpeg @4.2.1_2+gpl2 ---> Cleaning ffmpeg ---> Updating database of binaries ---> Scanning binaries for linking errors ---> No broken files found. ---> No broken ports found. > On Dec 14, 2019, at 06:49, Andrew Udvare wrote: > > > > Sent fro

ffmpeg Fails After MacPorts Migration to Catalina Version

I’ve been using ffmpeg daily for several years to generate time lapse videos from a series of JPEGs. After I updated my 2017 iMac to Catalina, it still worked. However, after migrating MacPorts to the Catalina version, it fails: ./skyvideo.sh: line 38: 5438 Donecat $ipath

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

I saved the version of ffmpeg that was built before I migrated and which worked fine before migration. It also now fails with the same error message. So, I think there’s something else going on here > On Dec 14, 2019, at 08:16, Andrew Udvare wrote: > > It's built so it seems more likely this

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

I tried uninstalling all ports and reinstalling again. That didn’t work. I did manage to get my time-lapse videos working with avconv.

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

These work: /usr/local/bin/avconv -y -r 10 -i $inpath -r 10 -vcodec libx264 -q:v 3 $vfile; /usr/local/bin/ffmpeg -y -r 10 -i $inpath -r 10 -vcodec libx264 -q:v 3 $vfile; This doesn’t: /opt/local/bin/ffmpeg -y -r 10 -i $inpath -r 10 -vcodec libx264 -q:v 3 $vfile; Both ffmpegs are version 4.2.1

Re: ffmpeg Fails After MacPorts Migration to Catalina Version

There are two recent tickets which, I believe, involve the same error: ffmpeg and ffmpeg-devel immediately crash with segfault 11 when input is mp4: https://trac.macports.org/ticket/59750 ffmpeg @4.2.1 crash using -vcodec libx264:

MacPorts 2.6.2: Failed to configure postgresql83

I have no idea what to do about this. The error message includes: Error: Failed to configure postgresql83, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_databases_postgresql83/postgresql83/work/postgresql-8.3.23/config.log Error:

Re: MacPorts 2.6.2: Failed to configure postgresql83

On Oct 22, 2019, at 16:00, Ryan Schmidt wrote: > > Yes, looks like nothing depended on postgresql83-server. > > >> Any way of finding out why this got installed in the first place? It didn't >> seem to have any dependencies, so why was it there? > > It was installed either because you

Re: MacPorts 2.6.2: Failed to configure postgresql83

> On Oct 22, 2019, at 13:45, Ryan Schmidt wrote: > > > > On Oct 22, 2019, at 00:50, Michael Newman wrote: > >>> On Oct 22, 2019, at 12:26, Wahlstedt Jyrki wrote: >>> Michael Newman kirjoitti 22.10.2019 kello 7.19: I have no idea. I don’t even know what it is. It must have

Re: MacPorts 2.6.2: Failed to configure postgresql83

> On Oct 22, 2019, at 12:26, Wahlstedt Jyrki wrote: > >> Michael Newman kirjoitti 22.10.2019 kello 7.19: >> >> I have no idea. I don’t even know what it is. It must have been installed by >> some other port that I requested. > > Hi, > can you find out, what it was you requested. I looked at

Re: MacPorts 2.6.2: Failed to configure postgresql83

"Dominic Reich" mailto:domi...@mm.st>> wrote: > You should be able to print without any additional software (except the > driver that macOS retrieves from its Servers). But you won't need any > package from MacPorts for printing. > > Besides that, postgresql83-server is a database. You won't

Re: mpv, ffmpeg seg fault in macOS catalina

I’m sorry, but I don’t understand most of what was written in this thread, but I do have a simple question: If I upgrade to Catalina (I already have Xcode 11.1) and install MacPorts for Catalina will ffmpeg stop working? > On Oct 18, 2019, at 19:00, Gill Bates > wrote:

Re: mpv, ffmpeg seg fault in macOS catalina

Thanks. I’ve used the migration process many times in the past, so no worries. I appreciate your taking the time to reply. > On Oct 19, 2019, at 10:08, Chris Jones wrote: > >> If I upgrade to Catalina (I already have Xcode 11.1) and install MacPorts >> for Catalina will ffmpeg stop working? >

Re: MacPorts 2.6.2: Failed to configure postgresql83

>> On Oct 22, 2019, at 16:00, Ryan Schmidt > > wrote: >>> >>> Yes, looks like nothing depended on postgresql83-server. > > Except the Mac printing system. I managed to get the printers back by resetting the printer system.

Re: MacPorts 2.6.2: Failed to configure postgresql83

> On Oct 22, 2019, at 16:00, Ryan Schmidt > wrote: >> >> Yes, looks like nothing depended on postgresql83-server. Except the Mac printing system. After deleting postgresql83-server I can no longer print. My printer has disappeared from the "Printers & Scanners

Re: MacPorts 2.6.2: Failed to configure postgresql83

> On Oct 22, 2019, at 11:06, Wahlstedt Jyrki wrote: > > Hi, > just being curious, why postgresql83? It was EOL’d several years ago, so it > is obsolete. If you want PostgreSQL, the current version is postgresql12. I have no idea. I don’t even know what it is. It must have been installed by

sudo port selfupdate Doesn't Seem To Work

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 MacPorts release in /opt/local as

Re: sudo port selfupdate Doesn't Seem To Work

Yes. That was it. It failed because I had not yet accepted the Xcode license. Once I did that 2.6.1 was actually installed and I was able upgrade installed ports. Thank you. > On Oct 6, 2019, at 07:26, Joshua Root wrote: > > Michael Newman wrote: >> What’s going on here? >> >> --->

/usr/local/bin/lynx: Bad CPU type in executable

MacPorts Version: 2.6.2 macOS 10.15.2 I installed lynx today and received the error message: /usr/local/bin/lynx: Bad CPU type in executable Is there anything I can do about this? MacPorts is up to date: MrMuscle:~ mnewman$ sudo port upgrade outdated Nothing to upgrade. ---> Scanning

/usr/local/bin/lynx: Bad CPU type in executable

Sorry. I used the wrong version of Lynx…. MacPorts Version: 2.6.2 macOS 10.15.2 I installed lynx today and received the error message: /usr/local/bin/lynx: Bad CPU type in executable Is there anything I can do about this? MacPorts is up to date: MrMuscle:~ mnewman$ sudo port upgrade outdated

Re: /usr/local/bin/lynx: Bad CPU type in executable

More of the story. When I got up this morning I found that a couple of scripts that I run overnight had failed with error 127. It seems that the scripts couldn’t find curl. So I checked, and sure enough, curl was missing. No worries, I can reinstall it. And then I wonder, what else is

Re: /usr/local/bin/lynx: Bad CPU type in executable

On Dec 22, 2019, at 22:04, Ryan Schmidt wrote: > Since reclaim prints a list of the ports it will remove, it seems like it's > up to you to verify that there isn't anything on the list that you want to > keep before confirming the action, and it should not be surprising or scary > to you

Re: /usr/local/bin/lynx: Bad CPU type in executable

On Dec 23, 2019, at 21:06, Ryan Schmidt wrote: > > As far as I know, yes it does, by default, which is why, if you install them > to their default locations, you should only use one package manager and > uninstall the other to prevent conflicts. I supposed that in an ideal world where a

Re: Is It Safe To Use reclaim?

Thanks to all for the clearly written suggestions. At this point I don't understand most of this well enough to have any confidence that I won't mess things up worse than they already are. I'm not much concerned about storage, so I think my best course of action here is to disable the reclaim

Re: Is It Safe To Use reclaim?

> On May 3, 2020, at 21:28, Ryan Schmidt wrote: > > Look at the output of "port installed unrequested". If you see any port in > that list that you actually do want, indicate that by running "sudo port > setrequested thePortName". This is easier said than done. The output of port installed

Is It Safe To Use reclaim?

Late last year I ran reclaim for the first time. It was somewhat of a disaster because it removed ports that I actually wanted and I ended up having to completely reinstall MacPorts. Since then I have been afraid to use it again. As far as I can tell there is no way for me to be sure that

Re: Failed to build graphviz: command execution failed

> On Sep 3, 2020, at 22:01, Ryan Schmidt wrote: > > There have been a few other reports lately of graphviz build failures for > other reasons; if you're experiencing a graphviz build failure, see if one of > them applies. I spent some time searching around, but all I found were other

Re: Failed to build graphviz: command execution failed

> On Sep 4, 2020, at 05:51, Ryan Schmidt wrote: > >> Warning: cltversion: For a possible fix, please see: >> https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt >> > > Follow the instructions at that URL. Thank you.

Re: Failed to build graphviz: command execution failed

> On Sep 4, 2020, at 07:27, Ryan Schmidt wrote: > > It's especially non-straightforward when Apple breaks things, like removing > the receipt of the command line tools periodically, which is what that > problem hotlist entry is about. OK, now I understand why what I tried didn't work and why

Failed to build graphviz: command execution failed

I realize that there is a ticket on this (57137) that has been open for quite some time. However, this is the first time I've seen this error. What concerns me is this: MrMuscle:~ mnewman$ port rdependents graphviz The following ports are dependent on graphviz: vala gssdp gupnp

Warning: All compilers are either blacklisted or unavailable

Some months ago I upgraded the OS on a remote 2010 MacBook (the white one) to High Sierra (10.13.16). After the upgrade I did the recommended MacPorts migration without problems. I don’t visit this machine very regularly, so only recently remembered to run port clean all after doing a

Re: Warning: All compilers are either blacklisted or unavailable

On Jan 1, 2021, at 01:47, Ryan Schmidt wrote: > If you see this warning when doing actions other than > configuring/building/installing (such as when cleaning) ignore it. Maybe we > shouldn't even display the warning in those cases, though I'm not sure if > there's a good way for us to do

Warning: Configuration logfiles contain indications of -Wimplicit-function-declaration

Today I finally installed Big Sur and followed the MacPorts migration guide. I don't see any errors; no failures to build. However, I did get seven of these warnings: Warning: Configuration logfiles contain indications of -Wimplicit-function-declaration; check that features were not

Warning: cltversion:....

This happens both on a 2017 iMac running Catalina and a 2010 MBA running High Sierra. Every time I run "sudo port upgrade outdated" I get the message about the command line tools: "Warning: cltversion: The Command Line Tools are installed, but MacPorts cannot determine the version." I follow

Error: Failed to build librsvg: command execution failed

Old 2010 MacBook Air on: 10.13.6 MacPorts: 2.7.1 CLTools: 10.1.0.0.1.1539992718 Here's the error: Error: Failed to build librsvg: command execution failed Error: See

Re: Error: Failed to build librsvg: command execution failed

> On Oct 13, 2021, at 18:12, Lenore Horner wrote: > > Do you have /opt/local/bin/clang-mp-11? Axe:~ mnewman$ ls /opt/local/bin/clang-mp-11 ls: /opt/local/bin/clang-mp-11: No such file or directory > On Oct 13, 2021, at 19:31, Christopher Jones wrote: > > oh, and to be sure please first run

Re: Error: Failed to build librsvg: command execution failed

> On Oct 13, 2021, at 20:28, Christopher Jones wrote: > > In the meantime if you are in a hurry installing macports clang 11 should > also fix things. I wasn't in a hurry, but I wanted to try this. It worked. Thank you very much. Mike

ffmpeg unexpectedly uninstalled

When I periodically update MacPorts I also run: sudo port -f uninstall inactive This seemed to work fine until last month when ffmpeg was uninstalled. I reinstalled and forgot about it. But, it happened again yesterday: ---> Deactivating ffmpeg @4.4.1_1+gpl2 ---> Cleaning ffmpeg --->

Re: ffmpeg unexpectedly uninstalled

Jan 2022, at 11:54 pm, Michael Newman via macports-users >> wrote: >> >> When I periodically update MacPorts I also run: >> >> sudo port -f uninstall inactive > > Why are you using the -f option here. That could force something to happen > that might

Migrating After Sonoma Install

Don’t worry. The migration went fine and, fingers crossed, everything works. However, it always amazes me how long this takes. I have only 13 ports in requested.txt. There are 148 ports in myports.txt. I get this, but I still find it amazing. On a 2019 Intel iMac, the migration started at

Warning: Error parsing file...

I recently had to reformat my boot drive, reinstall MacOS and restore from a CCC backup. After doing so I ran: sudo port -u upgrade outdated And received many warnings like this: ---> Scanning binaries for linking errors Warning: Error parsing file /opt/local/bin/msgcmp: Error opening or

py310-markdown - Failed to fetch signature for archive

After: sudo port -u upgrade outdated Error: Failed to archivefetch py310-markdown: Failed to fetch signature for archive: The requested URL returned error: 503 Then: sudo port install py310-markdown ---> Computing dependencies for py310-markdown ---> Fetching archive for py310-markdown --->

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

When upgrading MacPorts this morning I noticed the following message wizzing by: Warning: Configuration logfiles contain indications of -Wimplicit-function-declaration; check that features were not accidentally disabled: This right after: ---> Configuring xorg-libxcb I've never seen

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

Thank you for the explanation. I tried to read the wiki page. Unfortunately, it is above my pay grade. I'll have to leave it to someone else to file a ticket. > On May 7, 2022, at 12:48, Joshua Root wrote: > > We have a wiki page with an in-depth explanation of what this warning means: >