Opened 6 years ago

Closed 6 years ago

#57088 closed defect (invalid)

Problem using macports to install octave

Reported by: FLeve81 Owned by: MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Priority: Normal Milestone:
Component: ports Version: 2.5.3
Keywords: Cc:
Port: octave

Description (last modified by Schamschula (Marius Schamschula))

I am using the newest version of macports and I have Xcode, Xcode command line tools and the newest gcc. I tried to install Octave from macports in the terminal window and I get the following error

-----------
Fredericks-MBP:~ frederickleve$ sudo port install octave
Warning: MacPorts is configured to use an unsigned source for the ports tree. Please edit sources.conf and change 'rsync://rsync.macports.org/release/ports/' to 'rsync://rsync.macports.org/release/tarballs/ports.tar'.
Warning: MacPorts is configured to use an unsigned source for selfupdate. Please edit macports.conf and change the rsync_dir setting to match macports.conf.default.
Warning: xcodebuild exists but failed to execute
Error: Requested variants "+accelerate+app+docs+gfortran+graphicsmagick+qt5+sound+sundials" do not match those the build was started with: "+app+atlas+docs+gfortran+graphicsmagick+qt5+sound+sundials".
Error: Please use the same variants again, or run 'port clean octave' first to remove the existing partially completed build.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port octave failed
-------------------

Can someone tell me what to do here. I tried altering the sources.conf files and that did not work.

Change History (5)

comment:1 Changed 6 years ago by Schamschula (Marius Schamschula)

Description: modified (diff)
Keywords: octave macports 2.5.3 install fail removed
Port: octave added

The warning is not your issue here. The problem is that you changed the selected variants along the way:

+accelerate+app+docs+gfortran+graphicsmagick+qt5+sound+sundials != +app+atlas+docs+gfortran+graphicsmagick+qt5+sound+sundials

Please run sudo port clean octave and then try installing again.

BTW: +atlas is pointless for any recent version of macOS.

comment:2 Changed 6 years ago by FLeve81

Fredericks-MBP:~ frederickleve$ sudo port clean octave
Warning: MacPorts is configured to use an unsigned source for the ports tree. Please edit sources.conf and change 'rsync://rsync.macports.org/release/ports/' to 'rsync://rsync.macports.org/release/tarballs/ports.tar'.
Warning: MacPorts is configured to use an unsigned source for selfupdate. Please edit macports.conf and change the rsync_dir setting to match macports.conf.default.
Warning: xcodebuild exists but failed to execute
--->  Cleaning octave
Fredericks-MBP:~ frederickleve$ 

This is what I get when I try to clean the port. Also, I forced macports to use gcc-4.2 through

sudo port clean sam2p
sudo port install sam2p configure.compiler=macports-llvm-gcc-4.2

to see if it got rid of the warnings.

Last edited 6 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:3 in reply to:  2 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to FLeve81:

Fredericks-MBP:~ frederickleve$ sudo port clean octave
Warning: MacPorts is configured to use an unsigned source for the ports tree. Please edit sources.conf and change 'rsync://rsync.macports.org/release/ports/' to 'rsync://rsync.macports.org/release/tarballs/ports.tar'.
Warning: MacPorts is configured to use an unsigned source for selfupdate. Please edit macports.conf and change the rsync_dir setting to match macports.conf.default.
Warning: xcodebuild exists but failed to execute
--->  Cleaning octave
Fredericks-MBP:~ frederickleve$ 

This is what I get when I try to clean the port.

Looks like the port cleaned successfully.

In addition, you are using an unsigned ports tree source, and should switch to a signed source as the error message explains.

In addition, there is a problem with your xcodebuild command which you will have to investigate and fix.

Also, I forced macports to use gcc-4.2 through

sudo port clean sam2p
sudo port install sam2p configure.compiler=macports-llvm-gcc-4.2

to see if it got rid of the warnings.

llvm-gcc-4.2 is not gcc-4.2. But both of those compilers are ancient and there should be no reason for you to need to try to use either of them on a recent version of macOS.

comment:4 Changed 6 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Owner: set to MarcusCalhoun-Lopez
Status: newaccepted

Have all the issues been resolved for this ticket?

comment:5 Changed 6 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Resolution: invalid
Status: acceptedclosed

Solutions have been offered to fix the problem.
However, there has been no response as to their efficacy.

Note: See TracTickets for help on using tickets.