[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11
Date: Tue, 14 Jan 2014 02:34:14 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130917 Firefox/17.0 Iceweasel/17.0.9

Follow-up Comment #17, bug #41067 (project octave):

The list that you added these items to is a list of tools (i.e., programs like
Perl, Mercurial, or AWK), not library dependencies.  Looking at it now, I see
that it doesn't include C, C++, and Fortran compilers, so I suppose those
should be listed.

The list of library dependencies already appears in the
doc/interpreter/install.txi file that is used to generate the INSTALL file. 
If that list is incomplete, then we should fix it.  But rather than duplicate
it in the etc/HACKING file, it would probably be better to just point to the

If you update the list of library dependencies in install.txi, I would prefer
to keep it generic (LAPACK, not liblapack-dev, since the former is the name of
the software and the latter is the name of a package on a particular operating

Looking at the install.txi file, I see that there is some duplication already
because the list of required tools also appears there.  I think it would be
better to avoid duplication, so maybe some rewriting of etc/HACKING is

In any case, listing the dependencies doesn't really fix the problem that was
originally reported.  If there is a crash because of a missing dependency, it
would be much better to fix Octave so that it doesn't crash even when the
dependency is missing, or if that's not possible, fix the configure script so
that it is impossible to configure Octave unless the dependency is available.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]