Opened 17 months ago

Last modified 17 months ago

#66422 new defect

failing to install gnuplot 5.4.3 apparently bc of llvm-3.7

Reported by: natelsonoptics Owned by:
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: gnuplot

Description (last modified by jmroot (Joshua Root))

Trying to install gnuplot on an M2 macbook pro running Monterey 12.6.1. I've iterated a few times, and in the end, everything gets hung up on this:

--->  Computing dependencies for llvm-3.7.
Error: Cannot install llvm-3.7 for the arch 'x86_64' because
Error: its dependency libedit cannot build for the required arch.
Error: Follow https://guide.macports.org/#project.tickets if you believe there
is a bug.
Error: Processing of port llvm-3.7 failed

Any advice on how to get llvm-3.7 installed as universal or for arm64 explicitly? As far as I can tell, everything else seems to be in place.

Attachments (1)

installed.txt (21.0 KB) - added by natelsonoptics 17 months ago.
output of sudo port -v installed

Download all attachments as: .zip

Change History (8)

comment:1 Changed 17 months ago by natelsonoptics

Description: modified (diff)

comment:2 Changed 17 months ago by kencu (Ken)

llvm-3.7 will most likely never be installable for arm64.

The trick here is to figure out why it is being called in, and stop that.

comment:3 Changed 17 months ago by jmroot (Joshua Root)

Description: modified (diff)

There's very little to go on here, but without further information (like a log or the output of port -v installed), my guess would be that you migrated from an x86_64 machine and need to follow wiki:Migration.

Changed 17 months ago by natelsonoptics

Attachment: installed.txt added

output of sudo port -v installed

comment:4 Changed 17 months ago by natelsonoptics

Thanks for taking a look, and apologies for the naive questions.

I've attached the output of sudo port -v installed.

This is not a migration; while I did migrate from a timemachine backup onto the M2 machine, I had never installed ports before.

I initially tried following the simple installation instructions; after that failed, I looked at the list of tickets and followed this approach:

sudo port clean gnuplot
sudo port selfupdate
sudo port upgrade outdated
sudo port install gnuplot

After iterating that a couple of times, which cleaned up almost everything, now when I run

sudo port -v install gnuplot

I get this:

--->  Computing dependencies for gnuplot.
--->  Cleaning gnuplot
--->  Removing work directory for gnuplot
--->  Scanning binaries for linking errors
Could not open /opt/local/lib/libffi.6.dylib: Error opening or reading file (referenced from /opt/local/libexec/llvm-3.7/bin/FileCheck)
--->  Found 160 broken files, matching files to ports
--->  Found 1 broken port, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt: llvm-3.7 @3.7.1
Continue? [Y/n]:

comment:5 Changed 17 months ago by natelsonoptics

Actually, when I run that sequence again, when I try to upgrade outdated, I get this:

Error: Cannot install llvm-9.0 for the arch 'x86_64' because
Error: its dependency libedit cannot build for the required arch.
Error: Problem while installing llvm-9.0
Error: Follow https://guide.macports.org/#project.tickets if you believe there
is a bug.

Clearly there are issues with calls to various previous versions of llvm somehow.

If there is a particular log that would be useful for me to generate, please tell me how, and I'll attach it.

Last edited 17 months ago by natelsonoptics (previous) (diff)

comment:6 Changed 17 months ago by kencu (Ken)

You have a bunch of ancient installed ports from 2016 that are x86_64 architecture. They slipped in on you somehow.

I would just start fresh, with:

sudo port -f uninstall installed
sudo port -v reclaim

and then install the ports you want.

comment:7 Changed 17 months ago by kencu (Ken)

you could try and do a cleanup project, but it's hard to get it right, and to be honest just reinstalling is safer.

The specific issue seems to be this ancient ld64 is still hanging around:

ld64-latest @253.3_2+llvm37

but even after cleaning that up, you may find issues.

Note: See TracTickets for help on using tickets.