[MacPorts] #57088: Problem using macports to install octave

MacPorts noreply at macports.org
Mon Sep 3 16:16:29 UTC 2018


#57088: Problem using macports to install octave
----------------------+--------------------
  Reporter:  FLeve81  |      Owner:  (none)
      Type:  defect   |     Status:  new
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.5.3
Resolution:           |   Keywords:
      Port:  octave   |
----------------------+--------------------

Comment (by ryandesign):

 Replying to [comment:2 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.

-- 
Ticket URL: <https://trac.macports.org/ticket/57088#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list