[MacPorts] #36146: octave-devel build: no graphics display found

[MacPorts]

#36146: octave-devel build: no graphics display found
---------------------------+-------------------------
  Reporter:  vic@…         |      Owner:  michaelld@…
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.1.2
Resolution:                |   Keywords:
      Port:  octave-devel  |
---------------------------+-------------------------

Comment (by vic@…):

 Replying to [comment:1 ryandesign@…]:
 > You will need to install X11—either [http://xquartz.macosforge.org/
 Xquartz] or the xorg-server port; have you done this already? What is the
 DISPLAY environment variable set to?
 >
 > You mentioned Homebrew. Do you have Homebrew (and thus things in
 /usr/local) installed at the same time that you're using MacPorts? That's
 not supported and will cause problems. Please choose one package manager
 to use, and uninstall the other.
 Xquartz is installed. It has been since I installed Mountain Lion, some
 time ago.
 DISPLAY?
 {{{
 ~$ echo $DISPLAY
 /tmp/launch-IMFoxP/org.macosforge.xquartz:0
 }}}
 I don't believe there is any conflict with the Homebrew Octave on my
 system. My PATH reads
 {{{
 ~$ echo $PATH
 /usr/texbin:/opt/local/libexec/gnubin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin
 }}}
 MacPorts Octave is what I get with the command
 {{{
 ~$ octave
 }}}
 I can only get the Homebrew Octave with the very specific
 {{{
 ~$ /usr/local/bin/octave
 }}}
 unless the MacPorts Octave is dead. In any case, the two Octaves can run
 different projects independently. If it weren't for my Homebrew Octave, I
 wouldn't have had any Octave at all recently. The Homebrew Octave didn't
 get killed by the recent upgrade of gcc in MacPorts.

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