Re: Trying to compile Octave on RHEL 7.3

[Michael Metts]

hey Mike.  if i SU to root and run ./run-octave it seems to work just fine - 
i.e. command window is NOT blank with black dots.  i’m still trying to figure 
out what the difference is.  where does Octave hide user settings?  for 
instance, when i ran it as root it gave me the intro screens.  when run it as 
myself it doesn’t not.  i’m wondering if there’s some old file that i should 
erase.  all i found in ~/ was .octave_hist … 

i’m happy to open a bug report too.  i tried comparing the results of env > 
myenv side by side to see if there’s something funny about root vs. me … 
nothing i didn’t already know about or expect.  i’ll keep digging.  

> On Mar 2, 2017, at 12:03 PM, Mike Miller <address@hidden> wrote:
> 
> On Thu, Mar 02, 2017 at 11:24:28 -0800, Michael Metts wrote:
>> So I downloaded 4.2.1 from the ftp site and built it.  the build was
>> clean but when i say ./run-octave get a command window that’s full of
>> black dots.  when type, the characters are invisible.  if i press
>> enter, the command is executed and appears in the command history pane
>> but the command window itself is just a sea of black dots.  if i clear
>> it, i can see the cursor to the top but all the dots are just as they
>> were.  so close and yet so far.  i’ll run the make tests but i wonder
>> if there’s something else i’m missing here.
> 
> We should take this to the bug tracker. There have been a handful of bug
> reports about the command window being blank, but no definitive
> resolution that I know of.
> 
> Can you file a bug report at
>  https://savannah.gnu.org/bugs/?func=additem&group=octave
> 
> No need to create an account if you don't want to. Please give the
> details about the Qt 4 package versions that you gave here, and attach a
> screenshot if you can. I don't have a CentOS/RHEL 7 to try to reproduce
> on at the moment, but maybe someone else can. If you pass "-cli" to
> run-octave, you can use Octave in its original non-GUI form.
> 
> -- 
> mike