Opened 19 months ago

Closed 6 weeks ago

#65973 closed defect (worksforme)

gnuplot @5.4.3 build failure

Reported by: basriaz Owned by: mojca (Mojca Miklavec)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: ryandesign (Ryan Carsten Schmidt), mascguy (Christopher Nielsen), jeremyhu (Jeremy Huddleston Sequoia)
Port: gnuplot cairo xorg-libX11

Description (last modified by jmroot (Joshua Root))

I'm trying to install gnuplot on macOSX (high sierra) using macports:

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

I got this error message:

--->  Computing dependencies for gnuplot
--->  Fetching archive for gnuplot
--->  Attempting to fetch gnuplot-5.4.3_0+aquaterm+luaterm+pangocairo+wxwidgets+x11.darwin_17.x86_64.tbz2 from http://packages.macports.org/gnuplot
--->  Attempting to fetch gnuplot-5.4.3_0+aquaterm+luaterm+pangocairo+wxwidgets+x11.darwin_17.x86_64.tbz2 from http://fra.de.packages.macports.org/gnuplot
--->  Attempting to fetch gnuplot-5.4.3_0+aquaterm+luaterm+pangocairo+wxwidgets+x11.darwin_17.x86_64.tbz2 from http://nue.de.packages.macports.org/gnuplot
--->  Building gnuplot
Error: Failed to build gnuplot: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_gnuplot/gnuplot/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
Error: Processing of port gnuplot failed

How do I fix this error?

Attachments (1)

main.log (629.0 KB) - added by basriaz 19 months ago.

Download all attachments as: .zip

Change History (7)

comment:1 Changed 19 months ago by jmroot (Joshua Root)

Description: modified (diff)
Owner: set to mojca
Port: gnuplot added
Status: newassigned
Summary: gnuplot failedgnuplot @5.4.3 build failure

Please attach the log.

Changed 19 months ago by basriaz

Attachment: main.log added

comment:2 Changed 19 months ago by jmroot (Joshua Root)

Cc: ryandesign mascguy jeremyhu added
Port: cairo xorg-libX11 added
:info:build dyld: Library not loaded: /opt/local/lib/libX11.6.dylib
:info:build   Referenced from: /opt/local/lib/libcairo.2.dylib
:info:build   Reason: Incompatible library version: libcairo.2.dylib requires version 11.0.0 or later, but libX11.6.dylib provides version 10.0.0

Not sure how that would have happened. The binary for xorg-libX11 has compatibility version 11 as expected:

% otool -L xorg-libX11-1.8.1_0.darwin_17.x86_64/opt/local/lib/libX11.6.dylib 
xorg-libX11-1.8.1_0.darwin_17.x86_64/opt/local/lib/libX11.6.dylib:
	/opt/local/lib/libX11.6.dylib (compatibility version 11.0.0, current version 11.0.0)
	/opt/local/lib/libxcb.1.dylib (compatibility version 3.0.0, current version 3.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.50.4)

comment:3 Changed 19 months ago by basriaz

How do I solve the problem?

comment:4 Changed 19 months ago by basriaz

How do I fix this error?

comment:5 Changed 8 months ago by ryandesign (Ryan Carsten Schmidt)

Sounds like maybe something replaced your libX11.6.dylib with an older version without MacPorts knowing. To fix that specific problem, you could force MacPorts to reinstall that port. First, make sure your ports are up to date:

sudo port selfupdate
sudo port upgrade outdated

Then, using port provides /opt/local/lib/libX11.6.dylib to discover which port provided the file that got replaced, you could then run:

sudo port -n upgrade --force xorg-libX11

However, if xorg-libX11's files got replaced, who knows how many other ports' files got replaced. You would have to do the same for those. If you can't identify all the files that got replaced that need reinstalling, or can't explain how the files got replaced, maybe the safest thing to do is to uninstall MacPorts and then reinstall the ports you want; the migration instructions provide some guidance on how to do that.

comment:6 Changed 6 weeks ago by kencu (Ken)

Resolution: worksforme
Status: assignedclosed

nothing for macports to fix here without further information, which is not forthcoming after 18 months.

please reopen with new information if this is still an issue for you

Note: See TracTickets for help on using tickets.