[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11 |
Date: |
Tue, 14 Jan 2014 02:49:57 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36 |
Follow-up Comment #18, bug #41067 (project octave):
Yes, I'm still treating this bug as "Octave segfaults when built with some set
of dependency libraries". I'd rather not close this bug until I figure out
what the problem is (or give up and blame it on old versions of Qt and curl in
Ubuntu 12.04). Either way, I'm still digging into that for now.
I have been able to confirm that adding curl to my original build that was
segfaulting now allows the GUI to come up, I get the welcome wizard, all is
good.
I also agree with jwe about the patch. The "etc/HACKING" file is supposed to
be "here are things that developers hacking on Octave (== building Octave from
mercurial) need, that most users building from a source tarball don't need".
BLAS, LAPACK, and PCRE are things that everyone needs to build Octave, not
just hackers.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?41067>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11, (continued)
- [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11, Mike Miller, 2014/01/09
- [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11, Mike Sander, 2014/01/10
- [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11, Mike Miller, 2014/01/10
- [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11, John W. Eaton, 2014/01/10
- [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11, Mike Sander, 2014/01/10
- [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11, Mike Sander, 2014/01/11
- [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11, Mike Sander, 2014/01/13
- [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11, Mike Miller, 2014/01/13
- [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11, Mike Sander, 2014/01/13
- [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11, John W. Eaton, 2014/01/13
- [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11,
Mike Miller <=
- [Octave-bug-tracker] [bug #41067] "run-octave --force-gui" octave exited with signal 11, John W. Eaton, 2014/01/13
- [Octave-bug-tracker] [bug #41067] GUI exits immediately with signal 11 if built without libcurl, Mike Miller, 2014/01/13
- [Octave-bug-tracker] [bug #41067] GUI exits immediately with signal 11 if built without libcurl, John W. Eaton, 2014/01/14
- [Octave-bug-tracker] [bug #41067] GUI exits immediately with signal 11 if built without libcurl, Mike Sander, 2014/01/14
- [Octave-bug-tracker] [bug #41067] GUI exits immediately with signal 11 if built without libcurl, Mike Miller, 2014/01/14
- [Octave-bug-tracker] [bug #41067] GUI exits immediately with signal 11 if built without libcurl, John W. Eaton, 2014/01/14
- [Octave-bug-tracker] [bug #41067] GUI exits immediately with signal 11 if built without libcurl, Mike Sander, 2014/01/14
- [Octave-bug-tracker] [bug #41067] GUI exits immediately with signal 11 if built without libcurl, John W. Eaton, 2014/01/14
- [Octave-bug-tracker] [bug #41067] GUI exits immediately with signal 11 if built without libcurl, John W. Eaton, 2014/01/15
- [Octave-bug-tracker] [bug #41067] GUI exits immediately with signal 11 if built without libcurl, Mike Miller, 2014/01/15