[MacPorts] #38694: octave @3.2.4 -- failure during build compiling oct-alloc.cc

MacPorts noreply at macports.org
Tue Apr 23 11:34:21 PDT 2013


#38694: octave @3.2.4 -- failure during build compiling oct-alloc.cc
---------------------+--------------------------------
  Reporter:  cwr@…   |      Owner:  macports-tickets@…
      Type:  defect  |     Status:  closed
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:  2.1.3
Resolution:  fixed   |   Keywords:
      Port:  octave  |
---------------------+--------------------------------

Comment (by cwr@…):

 Let me just chime in as the original complainer. I absolutely do not care
 about "octave" versus "octave-devel". I just wanted SOME copy of Octave to
 use in my work. (Which, after help from michaelld in another thread, is
 going well.)

 My only concern is that anyone who wanders in like I did, having no prior
 experience with MacPorts, would assume that the port with the unqualified
 name ("octave") would be the place to start. That may lead to some problem
 that is hard for the new user to diagnose. Is there any way to mark the
 "octave" port as obsolete or deprecated or somehow suggest that you
 probably want to be using "octave-devel"?

-- 
Ticket URL: <https://trac.macports.org/ticket/38694#comment:9>
MacPorts <http://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list