[MacPorts] #62868: arb @6.0.2: ARBHOME: unbound variable

[MacPorts]

#62868: arb @6.0.2: ARBHOME: unbound variable
-------------------------+--------------------
  Reporter:  Channy-736  |      Owner:  (none)
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.6.4
Resolution:              |   Keywords:
      Port:  arb         |
-------------------------+--------------------

Comment (by ryandesign):

 Replying to [comment:10 Channy-736]:
 > {{{
 > /opt/local/bin/arb: line 55:
 Fusion.app/Contents/Public:/opt/X11/bin:/Library/Apple/usr/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:
 No such file or directory
 > }}}

 Your PATH contains a value containing spaces, specifically
 /Applications/VMware Fusion.app/Contents/Public, and the arb launch script
 contains a bug that causes it to be unable to handle that.

 They fixed this last year:

 http://bugs.arb-home.de/changeset/18439

 but the last version of arb that was released is from 5 years ago, so this
 fix is not in MacPorts yet.

 I don't know how much of a problem this is. It does not prevent the
 program from launching when I try it on my system.

 The real problem in your case is:

 > {{{
 > Error: Can't open display: :0
 > Error: Can't open display: :0
 > }}}

 The display should not be ":0". It should be a randomly generated path
 that, when accessed, causes X11.app to launch.

 The xinit port should have set this up for you if you followed the steps
 it displayed:

 {{{
 $ port notes xinit
 --->  xinit has the following notes:
   To use MacPorts' X11 as the default server, install xorg-server, log
 out, and log back in.
 }}}

 If you did do that and it's still not working due to trying to use display
 ":0", check your shell startup file (probably ~/.zprofile but could be
 ~/.bashrc, ~/.bash_profile, or ~/.profile) for any line like "export
 DISPLAY=:0" that sets the display. If that's present, remove it. There was
 a bug in the MacPorts 2.6.4 installer for macOS Big Sur that caused this
 line to be added erroneously; see #61649. The MacPorts 2.7.0 installer
 will no longer make that mistake, but it will not clean up the mistake
 previously made by the 2.6.4 installer if you had used it.

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