[MacPorts] #35434: octave-devel @3.4.3 build failure in Mac OSX 10.8

MacPorts noreply at macports.org
Tue Aug 28 05:53:34 PDT 2012


#35434: octave-devel @3.4.3 build failure in Mac OSX 10.8
-----------------------------+----------------------------------------------
 Reporter:  vic@…            |       Owner:  michaelld@…           
     Type:  defect           |      Status:  new                   
 Priority:  Normal           |   Milestone:                        
Component:  ports            |     Version:  2.1.2                 
 Keywords:  mountainlion     |        Port:  octave-devel          
-----------------------------+----------------------------------------------

Comment(by g5pw@…):

 Replying to [comment:42 michaelld@…]:
 > So, I think if you're in octave, and you do
 > {{{
 > available_graphics_toolkits()
 > }}}
 > it will return a list of available toolkits that you can select from.
 If octave+fltk is installed, then 'fltk' should appear in this list; if it
 does, then you should be able to do:
 > {{{
 > graphics_toolkit('fltk')
 > }}}
 > to select it; I think I had to issue this command twice to get it to
 work.  Then do
 > {{{
 > plot (1:10)
 > }}}
 > to see what happens. It should be obvious if fltk is being used, or if
 some other toolkit is still in place.

 Well, it works for me!

 >
 > I'm not sure I follow the rest.  What I'm asking for is for folks who
 already use both octave and octave-* ports to: replace octave's Portfile
 with the new one here, install the new octave, then try installing and
 using some of the octave-* ports to verify that they both install and work
 as expected.

 I'm sorry: what I was saying is: if you install a octave-* port, it
 installs with the octave-devel port, too. So we must update the octave-*
 even if we keep the old octave port.

-- 
Ticket URL: <https://trac.macports.org/ticket/35434#comment:43>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list