Opened 4 years ago

Closed 4 years ago

#60851 closed defect (fixed)

libiio fails to build under MacOS 10.14.6

Reported by: mcquiggi (Kevin McQuiggin) Owned by: michaelld (Michael Dickens)
Priority: Normal Milestone:
Component: ports Version: 2.6.2
Keywords: Cc:
Port: libiio

Description (last modified by mf2k (Frank Schima))

Hi There:

I'm a longtime user of MacPorts, thanks to all you folks for creating this service and keeping the thousands of ports running!

I am a gnuradio user and am trying to install libiio and gr-iio on my system, which runs MacOS 10.14.6.

When I "port install libiio" I get the following messages and the port fails to install. It seems to build, but then fails due a problem with /opt/local/lib/python3.7:

START

iMac:~ mcquiggi$ sudo port clean libiio
--->  Cleaning libiio
iMac:~ mcquiggi$ sudo port install libiio
--->  Computing dependencies for libiio
--->  Fetching archive for libiio
--->  Attempting to fetch libiio-0.20_0+python37.darwin_18.x86_64.tbz2 from https://packages.macports.org/libiio
--->  Attempting to fetch libiio-0.20_0+python37.darwin_18.x86_64.tbz2 from https://ywg.ca.packages.macports.org/mirror/macports/packages/libiio
--->  Attempting to fetch libiio-0.20_0+python37.darwin_18.x86_64.tbz2 from http://aus.us.packages.macports.org/macports/packages/libiio
--->  Fetching distfiles for libiio
--->  Verifying checksums for libiio
--->  Extracting libiio
--->  Applying patches to libiio
--->  Configuring libiio
--->  Building libiio
--->  Staging libiio into destroot
Error: Failed to destroot libiio: error renaming "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_libiio/libiio/work/destroot/opt/local/lib/python3.7": no such file or directory
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_libiio/libiio/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port libiio failed
iMac:~ mcquiggi$ 

END

I have /opt/local/lib/python3.8, but indeed there is no /opt/local/lib/python3.7.

This seems to be a problem with the install script looking for Python 3.7 but not seeing it as I have Python 3.8.

Any help appreciated. Just wanted to let you know that the install portion of the port is broken.

Kevin McQuiggin mcquiggi@…

Attachments (2)

main.log (727.1 KB) - added by mcquiggi (Kevin McQuiggin) 4 years ago.
main.2.log (252.3 KB) - added by mcquiggi (Kevin McQuiggin) 4 years ago.
Latest main.log, after removing the errant libiio framework from /Library/Frameworks

Download all attachments as: .zip

Change History (13)

comment:1 Changed 4 years ago by michaelld (Michael Dickens)

Please attached the build log as noted toward the END portion of the noted text. I'm guessing this is a duplicate of #60669 ... just a guess without the build log!

comment:2 Changed 4 years ago by michaelld (Michael Dickens)

Owner: set to michaelld
Status: newassigned

Changed 4 years ago by mcquiggi (Kevin McQuiggin)

Attachment: main.log added

comment:3 Changed 4 years ago by mcquiggi (Kevin McQuiggin)

Hi Michael:

The build/install log has now been attached to this ticket!

Thanks in advance,

Kevin

comment:4 Changed 4 years ago by mf2k (Frank Schima)

Keywords: libiio 2.6.2 MacOS-10.14.6 removed

comment:5 Changed 4 years ago by mf2k (Frank Schima)

In the future, please use WikiFormatting.

comment:6 Changed 4 years ago by mf2k (Frank Schima)

Description: modified (diff)

comment:7 Changed 4 years ago by michaelld (Michael Dickens)

Looks like you have an alternative iio install as /Library/Frameworks/iio.framework/iio. Do you know how this got there? As it's in a macOS-standard search path (/Library/Frameworks/), CMake is finding it. If you don't need it, I'd recommend getting rid of it. Then you'll need to do:

sudo port clean libiio

before trying to install it again.

Changed 4 years ago by mcquiggi (Kevin McQuiggin)

Attachment: main.2.log added

Latest main.log, after removing the errant libiio framework from /Library/Frameworks

comment:8 Changed 4 years ago by mcquiggi (Kevin McQuiggin)

Hi Michael:

A bit of narrative to accompany my update - I removed the errant framework and tried to clean/build again. Same error. So I verified that the framework had been removed (dragged to Trash), rebooted the Mac, did another clean and build, with the same result.

Perhaps there is some "deinstall" process necessry to remove the framework or something; my Mac OS management skills are not great.

The old framework was left over from an attempt to install a package directly from Analog Devices without success. I installed it and tried it; no go, so I moved on to the MacPorts version of libiio. I just forgot to remove the leftovers from the failed direct install.

Sorry that this isn't "simple"!

Kevin

comment:9 Changed 4 years ago by michaelld (Michael Dickens)

Progress! The errant framework is no longer being found! Now, you need to do the following:

sudo port clean libiio
sudo port selfupdate

then, try installing libiio & this time it should work. I fixed this latest issue less than 24 hours ago :)

comment:10 Changed 4 years ago by mcquiggi (Kevin McQuiggin)

Hi Michael:

Success!

Thanks very much.

Kevin

comment:11 Changed 4 years ago by michaelld (Michael Dickens)

Resolution: fixed
Status: assignedclosed

Great. You're welcome & thanks for reporting back!

Note: See TracTickets for help on using tickets.