On 2023-07-17 15:43, Takashi Yano via Cygwin wrote:
On Mon, 17 Jul 2023 17:27:37 -0400
Bryan VanSchouwen wrote:
Hello.
I just tried performing a correlation matrix calculation with
Cygwin's Octave software (having successfully performed this calculation
previously on other similar data
On Mon, 17 Jul 2023 17:27:37 -0400
Bryan VanSchouwen wrote:
> Hello.
>
> I just tried performing a correlation matrix calculation with
> Cygwin's Octave software (having successfully performed this calculation
> previously on other similar data sets) using the following comm
Hello.
I just tried performing a correlation matrix calculation with
Cygwin's Octave software (having successfully performed this calculation
previously on other similar data sets) using the following commands within
Cygwin:
*(start of commands)*
[vansc@LAPTOP-OHN
nks for the suggestions. I had already installed the xorg server and all
> > the packages you mentioned. But nevertheless I get the errors reported in
> > the original email, both if I start octave from the shell or by using the
> > XDG menu which starts octave with the GUI.
> &
Fabio Rossi via Cygwin writes:
> I forgot to mention that the test machine is running Windows 10 Pro 64
> bit with a ATI FirePro 3800 graphics card.
That particular family of graphics chips has drivers that do not
implement (or incorrectly) certain functions that the level of OpenGL
support would
re is no more to cut
-- Antoine de Saint-Exupéry
On 2023-04-27 10:15, Fabio Rossi wrote:
Hello Brians,
thanks for the suggestions. I had already installed the xorg server and all the
packages you mentioned. But nevertheless I get the errors reported in the
original email, both if
Hello Brians,
thanks for the suggestions. I had already installed the xorg server and all the
packages you mentioned. But nevertheless I get the errors reported in the
original email, both if I start octave from the shell or by using the XDG menu
which starts octave with the GUI.
In particular
Hi Fabio,
Some packages include non-GUI or native GUI interfaces that do not require
window system support.
Others may dynamically support window systems if they are installed, or have
separate executables for console or GUI, as octave does: octave and octave-cli.
If you are using octave
I forgot to mention that the test machine is running Windows 10 Pro 64 bit with
a ATI FirePro 3800 graphics card. On the same machine, octave built for Windows
executes correctly the same command. I have observed the same behaviour also on
other Windows machines running Win7 or other graphic
I have installed latest test version of octave 8.2.0-1. When I try to plot
using a simple command like "plot(1,1)" I get the following errors from the
command line
$ octave
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-+user'
GNU Octave, versio
Test versions 8.2.0-1 of
octave
octave-devel
octave-doc
are available in the Cygwin distribution:
When the octave subpackage will also be rebuild and available
it will move to stable.
CHANGES
Latest upstream release.
https://octave.org/news/release/2023/04/13/octave-8.2.0-released.html
Test versions 8.1.0-1 of
octave
octave-devel
octave-doc
are available in the Cygwin distribution:
When the octave subpackage will also be rebuild and available
it will move to stable.
CHANGES
Latest upstream release.
https://octave.org/news/release/2023/03/07/octave-8.1.0-released.html
On 24/01/2023 11:50, Marco Atzeri via Cygwin wrote:
On 17.01.2023 12:29, Wyser Klaus wrote:
Hej Marco---
Thanks for your reply. I tried to send the cygcheck output to the
Cygwin mailing list last week, but the file was too big (2M) and the
post was rejected. I therefore put the file on a temp
On 17.01.2023 12:29, Wyser Klaus wrote:
Hej Marco---
Thanks for your reply. I tried to send the cygcheck output to the Cygwin
mailing list last week, but the file was too big (2M) and the post was
rejected. I therefore put the file on a temporary platform for file exchange:
http://exporter.nsc
; Skickat: den 12 januari 2023 16:19
> Till: Wyser Klaus
> Kopia: cygwin@cygwin.com
> Ämne: Re: octave doesn't work any longer with qt graphics toolkit
>
> On Thu, Jan 12, 2023 at 3:32 PM Wyser Klaus via Cygwin wrote:
> >
> > Hej---
> >
> > I got a new co
On Thu, Jan 12, 2023 at 3:32 PM Wyser Klaus via Cygwin wrote:
>
> Hej---
>
> I got a new computer in September and installed Cygwin/X11 and many more
> packages, among others Octave (I think it was 5.2 back then). I have been
> using cygwin and octave for 20 years already,
Hej---
I got a new computer in September and installed Cygwin/X11 and many more
packages, among others Octave (I think it was 5.2 back then). I have been using
cygwin and octave for 20 years already, so I'm not new to this. Well,
everything worked just fine until I happened to update
> - Original Message -
> I cannot see a plot with qt graphics_toolkit.
>
> >> graphics_tookit qt;
> >> plot(1:10);
>
> plot window is filed with black.
>
> I met this on two different PCs.
>
> On one PC,
> >> plot(1:10);
> Xlib: sequence lost (0x11a61 > 0x1a63) in reply type 0x0!
> Xlib
> - Original Message -
> Date: 2022/06/26 日 22:59
> Subject: Re: fltk does not work on cygwin version octave-6.4.0
> On 23/06/2022 00:05, Tatsuro MATSUOKA wrote:
> >
> > [132545.312] (II) AIGLX: Testing pixelFormatIndex 2
> > [132545.343] GL_VERSION: 1.
een 0
Usually, this is what happens when the driver your graphics chipset
isn't installed, it's just working in 'VGA mode'.
(Everything should still work, using the software OpenGL renderer, as if
the X server was started with -nowgl)
But this doesn't seem to be the
I cannot see a plot with qt graphics_toolkit.
>> graphics_tookit qt;
>> plot(1:10);
plot window is filed with black.
I met this on two different PCs.
On one PC,
>> plot(1:10);
Xlib: sequence lost (0x11a61 > 0x1a63) in reply type 0x0!
Xlib: sequence lost (0x11a76 > 0x1a78) in reply type 0x0!
Xli
> - Original Message -
> From: "Marco Atzeri"
> To: "Tatsuro MATSUOKA" "cygwin
> Date: 2022/06/23 木 10:19
> Subject: Re: fltk does not work on cygwin version octave-6.4.0
> >> You can test the GL behaviour with
> >>
> >>
On 23.06.2022 01:05, Tatsuro MATSUOKA wrote:
You can test the GL behaviour with
$ cygcheck -l mesa-demos | grep bin
/usr/bin/eglinfo
/usr/bin/es2_info
/usr/bin/glinfo
/usr/bin/glxgears
/usr/bin/glxinfo
/usr/bin/wglgears
/usr/bin/wglinfo
/usr/bin/xeglgears
$ cygcheck -l mesa-demos | grep b
> - Original Message -
> From: "Marco Atzeri"
> To: "Tatsuro MATSUOKA" "cygwin
> Date: 2022/06/23 木 04:33
> Subject: Re: fltk does not work on cygwin version octave-6.4.0
> On 22.06.2022 12:37, Tatsuro MATSUOKA wrote:
> >> -
On 22.06.2022 12:37, Tatsuro MATSUOKA wrote:
- Original Message -
From: "Tatsuro MATSUOKA"
To: "Marco Atzeri"; "cygwin
Date: 2022/06/22 水 12:53
Subject: Re: fltk does not work on cygwin version octave-6.4.0
- Original Message -
From: "Marco Atzeri&q
> - Original Message -
> From: "Tatsuro MATSUOKA"
> To: "Marco Atzeri"; "cygwin
> Date: 2022/06/22 水 12:53
> Subject: Re: fltk does not work on cygwin version octave-6.4.0
> > > - Original Message -
> > > From: "
> > - Original Message -
> > From: "Marco Atzeri"
> > To: "cygwin
> > Date: 2022/06/22 水 02:06
> > Subject: Re: fltk does not work on cygwin version octave-6.4.0
> > On 21.06.2022 07:15, Tatsuro MATSUOKA wrote:
> > > fltk does n
> - Original Message -
> From: "Marco Atzeri"
> To: "cygwin
> Date: 2022/06/22 水 02:06
> Subject: Re: fltk does not work on cygwin version octave-6.4.0
> On 21.06.2022 07:15, Tatsuro MATSUOKA wrote:
> > fltk does not work on cygwin version octave-6.
On 21.06.2022 07:15, Tatsuro MATSUOKA wrote:
fltk does not work on cygwin version octave-6.4.0
octave:1> graphics_toolkit fltk
octave:2> plot(1:10);
Insufficient GL support
error: unable to plot due to insufficient OpenGL support
plot windows flashes and disappear immediately
On 21/06/2022 12:18, Takashi Yano wrote:
On Tue, 21 Jun 2022 19:48:09 +0900 (JST)
Tatsuro MATSUOKA wrote:
From: "Takashi Yano"
To: "cygwin>
Cc: "Tatsuro MATSUOKA"
Date: 2022/06/21 火 18:45
Subject: Re: fltk does not work on cygwin version octave-6.4.0
On Tue
On Tue, 21 Jun 2022 20:18:00 +0900
Takashi Yano wrote:
> On Tue, 21 Jun 2022 19:48:09 +0900 (JST)
> Tatsuro MATSUOKA wrote:
> > > From: "Takashi Yano"
> > > To: "cygwin>
> > Cc: "Tatsuro MATSUOKA"
> > > Date: 2022/06/21 火 18:45
&
On Tue, 21 Jun 2022 19:48:09 +0900 (JST)
Tatsuro MATSUOKA wrote:
> > From: "Takashi Yano"
> > To: "cygwin>
> Cc: "Tatsuro MATSUOKA"
> > Date: 2022/06/21 火 18:45
> > Subject: Re: fltk does not work on cygwin version octave-6.4.0
>
> &g
> From: "Takashi Yano"
> To: "cygwin>
Cc: "Tatsuro MATSUOKA"
> Date: 2022/06/21 火 18:45
> Subject: Re: fltk does not work on cygwin version octave-6.4.0
> On Tue, 21 Jun 2022 14:15:12 +0900 (JST)
> Tatsuro MATSUOKA wrote:
> > fltk does not w
On Tue, 21 Jun 2022 14:15:12 +0900 (JST)
Tatsuro MATSUOKA wrote:
> fltk does not work on cygwin version octave-6.4.0
>
> octave:1> graphics_toolkit fltk
> octave:2> plot(1:10);
> Insufficient GL support
> error: unable to plot due to insufficient OpenGL support
>
fltk does not work on cygwin version octave-6.4.0
octave:1> graphics_toolkit fltk
octave:2> plot(1:10);
Insufficient GL support
error: unable to plot due to insufficient OpenGL support
plot windows flashes and disappear immediately
fltk graphics_toolkit works octave on native windows.
New versions of
x86/x86_64 arch
octave-communications-1.2.4-1
octave-control-3.4.0-1
octave-fits-1.0.8-0.2
octave-instrument-control-0.7.1-1
octave-interval-3.2.1-1
for Octave 6.4 are available in the Cygwin distribution:
ADVISE
To load any package before usage run
"pkg load &
New versions of
noarch
octave-ga-0.10.2-1
octave-generate_html-0.3.2-1
octave-matgeom-1.2.3-1
octave-optics-0.1.4-1
octave-splines-1.3.4-1
octave-statistics-1.4.3-1
x86/x86_64 arch
octave-communications-1.2.3-1
octave-control-3.3.1-1
octave-database-2.4.4-2
New versions 6.4.0-1 of
octave
octave-devel
octave-doc
are available in the Cygwin distribution:
CHANGES
Latest upstream release.
https://www.gnu.org/software/octave/news/release/2021/10/30/octave-6.4.0-released.html
GENERAL NOTE
there are 2 octave main binaries with multiple graphic
On Thu, 16 Sep 2021 15:44:06 -0400
Bryan VanSchouwen wrote:
> I just tried performing an analysis in the Octave software (GNU Octave,
> version 5.2.0), using the attached "dm" input file, and the following
> commands:
> load dm
> cdmt = cor(dm.')
>
> Howeve
Hello.
I just tried performing an analysis in the Octave software (GNU Octave,
version 5.2.0), using the attached "dm" input file, and the following
commands:
load dm
cdmt = cor(dm.')
However, I encountered the following error message:
error: 'cor' undefined near line
On 2021-09-10 09:52, ASSI wrote:
Takashi Yano via Cygwin writes:
h. Bracketed paste mode is enabled by default. There is a configure-time
option (--enable-bracketed-paste-default) to set the default to on or off.
Does libreadline7 (8.1) break compatibility with old one?
Reverting libreadlin
Takashi Yano via Cygwin writes:
>> h. Bracketed paste mode is enabled by default. There is a configure-time
>>option (--enable-bracketed-paste-default) to set the default to on or off.
> Does libreadline7 (8.1) break compatibility with old one?
> Reverting libreadline7 to 7.0.3-3 solves the iss
extended globbing and allows them to appear anywhere in a
>word.
>
> i. The history library has a new variable that allows applications to set the
>initial quoting state, so quoting state can be inherited from a previous
>line.
>
> j. Readline now allows applica
New versions of
octave-general2.1.1-1
octave-io 2.6.0-1
octave-statistics 1.4.2-1
octave-netcdf 1.0.13-1
are available in the Cygwin distribution:
ADVISE
To load any package before usage run
"pkg load "
see "help pkg" for de
New versions 5.2.0-1 of
octave
octave-devel
octave-doc
are available in the Cygwin distribution:
CHANGES
Latest upstream release.
https://www.gnu.org/software/octave/news/release/2020/01/31/octave-5.2.0-released.html
Full changes for 5.x series:
https://www.gnu.org/software/octave
Am 07.02.2020 um 22:47 schrieb Jay Abel:
I'm using tcsh and for some reason the default configuration for X11 keeps
leaving zombie dbus processes, none of which seem to be reachable. For
example, when running Octave I get an error that dbus wasn't replying. Now,
if within the open xt
I'm using tcsh and for some reason the default configuration for X11 keeps
leaving zombie dbus processes, none of which seem to be reachable. For
example, when running Octave I get an error that dbus wasn't replying. Now,
if within the open xterm window I type dbus-launch and then I
Am 30.01.2020 um 22:05 schrieb Brian Inglis:
On 2020-01-29 06:46, Takashi Yano wrote:
Hi Marco,
On Wed, 29 Jan 2020 13:19:11 +0100
Marco Atzeri wrote:
As Octave uses gnulib, it is possible that the changes in MS are causing
a different subset of gnulib to be used than before, may be exposing
On 2020-01-29 06:46, Takashi Yano wrote:
> Hi Marco,
>
> On Wed, 29 Jan 2020 13:19:11 +0100
> Marco Atzeri wrote:
>> As Octave uses gnulib, it is possible that the changes in MS are causing
>> a different subset of gnulib to be used than before, may be exposing
ush_stdin is set here in configure by:
>
> if ac_fn_c_try_run "$LINENO"; then :
> gl_cv_func_fflush_stdin=yes
> else
> gl_cv_func_fflush_stdin=no
> fi
>
> and the test code for this decision is as attached. conftest.c
> returns 0 in cygwin 3.0.7, while cygwin
Am 29.01.2020 um 16:39 schrieb Hans-Bernhard Bröker:
[Ooops, sent this to Takashi instead of the list, originally.]
Am 29.01.2020 um 14:46 schrieb Takashi Yano:
On Wed, 29 Jan 2020 13:19:11 +0100
Marco Atzeri wrote:
As Octave uses gnulib, it is possible that the changes in MS are causing
a
this decision is as attached. conftest.c
returns 0 in cygwin 3.0.7, while cygwin with commit 59362c80e3a
returns 5.
I am not sure why segfault occurs if fseeko is replaced.
Probably due to a bug in octave or cygwin.
--
Takashi Yano
#include
# include
int
main ()
{
FILE *f = fopen ("c
[Ooops, sent this to Takashi instead of the list, originally.]
Am 29.01.2020 um 14:46 schrieb Takashi Yano:
On Wed, 29 Jan 2020 13:19:11 +0100
Marco Atzeri wrote:
As Octave uses gnulib, it is possible that the changes in MS are causing
a different subset of gnulib to be used than before, may
On Jan 29 16:32, Corinna Vinschen wrote:
> On Jan 29 22:46, Takashi Yano wrote:
> > --- m4/fseeko.m4.orig 2020-01-29 21:39:37.280507900 +0900
> > +++ m4/fseeko.m42020-01-29 21:36:29.263747100 +0900
> > @@ -30,16 +30,19 @@
> > HAVE_FSEEKO=0
> >else
> > if test $WINDOWS_64_BIT
On Jan 29 22:46, Takashi Yano wrote:
> Hi Marco,
>
> On Wed, 29 Jan 2020 13:19:11 +0100
> Marco Atzeri wrote:
> > As Octave uses gnulib, it is possible that the changes in MS are causing
> > a different subset of gnulib to be used than before, may be exposing
On Wed, 29 Jan 2020 22:46:53 +0900
Takashi Yano wrote:
> On Wed, 29 Jan 2020 13:19:11 +0100
> Marco Atzeri wrote:
> > As Octave uses gnulib, it is possible that the changes in MS are causing
> > a different subset of gnulib to be used than before, may be exposing
> &
Hi Marco,
On Wed, 29 Jan 2020 13:19:11 +0100
Marco Atzeri wrote:
> As Octave uses gnulib, it is possible that the changes in MS are causing
> a different subset of gnulib to be used than before, may be exposing
> a latent bug or race.
>
> Unfortunately my old build tree was poll
he crash.
Corinna
If is a BUG, it seems at compilation time as it produces binary with
different behaviour than before.
I was not able to segfault the old binary, I have problem in
all new built binaries.
I assume the 1909 build 18363.592 2020-01-14 arisen it.
As Octave uses gnulib, it is p
On Jan 28 07:41, Marco Atzeri wrote:
> Am 27.01.2020 um 12:33 schrieb Takashi Yano:
> > On Mon, 27 Jan 2020 07:45:08 +0100
> > Marco Atzeri wrote:
> > > Can you and Takashi provide me your cygcheck.out so that I can look on
> > > possible difference that could influence the build behaviour.
> >
>
my experience also. I was not able to make crash the old (by one month)
version
Next step, after cygport inst is done: run the test with the executable
in cygport's "inst" directory (to bypass libtool): Success, again!
So I tried running the test via libtool, i.e. the run-octave
Am 29.01.2020 um 01:02 schrieb Hans-Bernhard Bröker:
So re-run it in gdb, via libtool (run-octave -g ...). Still crashes,
but I didn't manage to get around the SIGSEGV handler in octave. It
always caught the SEGV before gdb managed to get there.
So my finding, so far, would be that th
Am 25.01.2020 um 17:55 schrieb Marco Atzeri:
libinterp/corefcn/file-io.cc-tst
...fatal: caught signal Segmentation fault
-- stopping myself...
/bin/sh: line 1: 3771 Segmentation fault (core dumped) /bin/sh
../run-octave --norc --silent --no-history -p
Marco Atzeri writes:
> I just found that my W10 Home is 1909 build 18363.592 so probably was
> updated as your around mid Jan
>
> https://docs.microsoft.com/en-us/windows/release-information/
>
> But Corporate versions have different time table and patch
Enterprise is, yes.
> the one I have is Ve
Am 28.01.2020 um 18:25 schrieb ASSI:
Achim Gratz writes:
Same thing here…
Since some of the discussion revolved on Windows versions: that is on
Win10 Pro 1909, fully patched. I no longer have a system with 1809
since the period where you could hold up the update has expired
recently. There i
Achim Gratz writes:
> Same thing here…
Since some of the discussion revolved on Windows versions: that is on
Win10 Pro 1909, fully patched. I no longer have a system with 1809
since the period where you could hold up the update has expired
recently. There is an ISO image for Windows Server 2016
On Tue, 28 Jan 2020 07:41:43 +0100
Marco Atzeri wrote:
> So I am now almost sure that the recent MS updates changed/broke
> something in W10 Home. :-((
I have tried now in Win10 Home 1909, and segmentagion fault
has occured at the same place as you.
Microsoft Windows [Version 10.0.18363.592]
--
Am 27.01.2020 um 12:33 schrieb Takashi Yano:
On Mon, 27 Jan 2020 07:45:08 +0100
Marco Atzeri wrote:
Can you and Takashi provide me your cygcheck.out so that I can look on
possible difference that could influence the build behaviour.
Attached.
Thanks Takashi,
I duplicated your installation
what W10 feature release YYMM and/or build N are you on?
Betriebssystemname:Microsoft Windows 10 Home
Betriebssystemversion: 10.0.18363 Nicht
zutreffend Build
18363
Can anyone try to rebuild the Octave package and let me know
if the
a specific order or atomicity of certain operations, as
debugging will almost always serialize the execution to the point where
these types of errors do not manifest.
Regards,
Achim.
the other problem of debugging is that the backtrace is trash
after the segfault and that of course Octave is a
400 Kg
On Sun, 26 Jan 2020 11:24:50 +0100
Marco Atzeri wrote:
> Am 26.01.2020 um 06:11 schrieb Takashi Yano:
> > On Sun, 26 Jan 2020 11:42:28 +0900
> > Takashi Yano wrote:
> >> In my environment, at least segmentation fault does not occur.
> >> When I built octave, man
Am 26.01.2020 um 06:11 schrieb Takashi Yano:
On Sun, 26 Jan 2020 11:42:28 +0900
Takashi Yano wrote:
In my environment, at least segmentation fault does not occur.
When I built octave, many of non-mandatory libraries were not
installed. This might affect.
Now I added all libraries warned in
s, as
debugging will almost always serialize the execution to the point where
these types of errors do not manifest.
Regards,
Achim.
the other problem of debugging is that the backtrace is trash
after the segfault and that of course Octave is a
400 Kg gorilla with all its dependencies..
I wil
Marco Atzeri writes:
> at least I know that is not just my machine.
> When I released the package was
>
>
> libinterp/corefcn/file-io.cc-tst
> ... PASS 90/90
Based on the test name there may be an assumption built into the code
about how the filesystem behaves that is
...fatal: caught signal Segmentation fault
-- stopping myself...
/bin/sh: line 1: 3771 Segmentation fault (core dumped) /bin/sh
../run-octave --norc --silent --no-history -p
/cygdrive/d/cyg_pub/devel/octave/prova_311_510/octave-5.1.0-2.x86_64/build/test/mex
/cygdrive/d
On Sun, 26 Jan 2020 11:42:28 +0900
Takashi Yano wrote:
> In my environment, at least segmentation fault does not occur.
> When I built octave, many of non-mandatory libraries were not
> installed. This might affect.
Now I added all libraries warned in config.log, and rebuilt.
Some of te
On Sat, 25 Jan 2020 17:55:31 +0100
Marco Atzeriwrote:
>libinterp/corefcn/file-io.cc-tst
> ...fatal: caught signal Segmentation fault
> -- stopping myself...
> /bin/sh: line 1: 3771 Segmentation fault (core dumped) /bin/sh
> ../run-octave
fatal: caught signal Segmentation fault
> -- stopping myself...
> /bin/sh: line 1: 3771 Segmentation fault (core dumped) /bin/sh
> ../run-octave --norc --silent --no-history -p
> /cygdrive/d/cyg_pub/devel/octave/prova_311_510/octave-5.1.0-2.x86_64/build/test/mex
&
On 2020-01-25 09:55, Marco Atzeri wrote:
> Hi All,
> I have recently released Octave 5.1.0
>
> https://cygwin.com/ml/cygwin-announce/2020-01/msg00010.html
> https://cygwin.com/ml/cygwin-announce/2020-01/msg00011.html
>
> that I built and packaged around 28 of December with
Hi All,
I have recently released Octave 5.1.0
https://cygwin.com/ml/cygwin-announce/2020-01/msg00010.html
https://cygwin.com/ml/cygwin-announce/2020-01/msg00011.html
that I built and packaged around 28 of December without
any compilation and test issue.
Than I passed to build the next version
On Wed, 15 Jan 2020, 11:09 Takashi Yano, wrote:
> On Mon, 13 Jan 2020 21:02:46 +0100
> Marco Atzeri wrote:
> > New versions 5.1.0-1 of
> > octave
> > octave-devel
> > octave-doc
> > are available in the Cygwin distribution:
>
> After up
On Mon, 13 Jan 2020 21:02:46 +0100
Marco Atzeri wrote:
> New versions 5.1.0-1 of
> octave
> octave-devel
> octave-doc
> are available in the Cygwin distribution:
After upgrading octave and octave-devel to 5.1.0-1,
mkoctfile stopped working with error:
/usr/lib/gcc/i686-
New versions of
octave-bim-1.1.5-4
octave-bsltl-1.3.1-1
octave-cgi-0.1.2-4
octave-communications-1.2.2-1
octave-control-3.2.0-1
octave-database-2.4.4-1
octave-dataframe-1.2.0-3
octave-data-smoothing-1.3.0-5
octave-debuginfo-5.1.0-1
octave-divand-1.1.2-5
octave-doctest-0.7.0-1
octave-econometrics
New versions 5.1.0-1 of
octave
octave-devel
octave-doc
are available in the Cygwin distribution:
CHANGES
Latest upstream release.
https://www.gnu.org/software/octave/news/release/2019/03/01/octave-5.1-released.html
Full changes:
https://www.gnu.org/software/octave/NEWS-5.1.html
eb Arjen Markus:
> > Hello,
> >
> > when I updated my installation of Cygwin with Octave (4.2.2 to be
> > precise) and tried running it (while having an X server running), I
> > ran into a problem with D-bus:
> >
> > D-Bus library appears to be incorrectly s
Am 08.01.2019 um 03:49 schrieb Arjen Markus:
Hello,
when I updated my installation of Cygwin with Octave (4.2.2 to be
precise) and tried running it (while having an X server running), I
ran into a problem with D-bus:
D-Bus library appears to be incorrectly set up; failed to read machine
uuid
Hello,
when I updated my installation of Cygwin with Octave (4.2.2 to be
precise) and tried running it (while having an X server running), I
ran into a problem with D-bus:
D-Bus library appears to be incorrectly set up; failed to read machine
uuid: Failed to open "/etc/machine-id": No
Am 27.12.2018 um 09:59 schrieb Mark Geisert:
Marco Atzeri wrote:
Hi,
I am trying to understand if octave has a problem
with Cygwin X interface or it is a specific
issue on my new Laptop
Can someone make this test from octave
in a Xterm ?
available_graphics_toolkits()
graphics_toolkit("
Marco Atzeri wrote:
Hi,
I am trying to understand if octave has a problem
with Cygwin X interface or it is a specific
issue on my new Laptop
Can someone make this test from octave
in a Xterm ?
available_graphics_toolkits()
graphics_toolkit("fltk")
x=(0:360)*pi()/180;
y=sin(x);
Hi,
I am trying to understand if octave has a problem
with Cygwin X interface or it is a specific
issue on my new Laptop
Can someone make this test from octave
in a Xterm ?
available_graphics_toolkits()
graphics_toolkit("fltk")
x=(0:360)*pi()/180;
y=sin(x);
plot(x,y)
print -d
New versions of
octave-communications-1.2.2-0.2
octave-control-3.1.0a-1
octave-database-2.4.3-2
octave-econometrics-1.1.1-5
octave-fits-1.0.7-4
octave-fl-core-1.0.1-0.2
octave-general-2.1.0-2
octave-geometry-3.0.0-3
octave-gsl-2.1.1-2
octave-image-2.8.0-2
octave-instrument
New versions 4.4.1-1 of
octave
octave-devel
octave-doc
are available in the Cygwin distribution:
CHANGES
Latest upstream bugfix release.
https://www.gnu.org/software/octave/news/release/2018/08/09/octave-4.4.1-released.html
Full changes:
https://www.gnu.org/software/octave/NEWS-4.4
New versions of
octave-gsl-2.1.1-1
octave-image-2.8.0-1
octave-interval-3.2.0-1
octave-lssa-0.1.3-1
octave-optim-1.5.3-1
octave-parallel-3.1.3-1
octave-stk-2.5.1-1
are available in the Cygwin distribution:
ADVISE
To load any package before usage run
"pkg load "
see
On Thu, Jul 19, 2018 at 5:08 PM, James R. Phillips via cygwin wrote:
> Hello,
>
> After installing octave-4.4.0-2 via setup-x86_64, I notice that
> /usr/bin/octave is a console-only app, and that there is no octave-gui binary
> in the package, although it is referred to
Hello,
After installing octave-4.4.0-2 via setup-x86_64, I notice that /usr/bin/octave
is a console-only app, and that there is no octave-gui binary in the package,
although it is referred to in the release announcement for 4.4.0-1.
The GUI version of octave becomes ever more capable, and it
On 09/07/2018 02:22, William Mitchell wrote:
Nope, same result. In fact, diff says there is no difference between this
cygGL-1.dll and the one I downloaded a few days ago.
I bought this computer in October 2012. It's due to be replaced anyway;
certainly before the Windows 7 end-of-life a year
gt;> several .m programs which will need octave (or Matlab).
>>
>>
> I understood, but I am talking of octave graphics interface
>
> See also
> https://octave.org/doc/v4.4.0/Graphics-Toolkits.html
>
> have you tried to plot with another graphics interface ?
>
Am 7/9/2018 um 2:55 AM schrieb William Mitchell:
Yes, I use gnuplot and xmgrace in other situations. But here I have
several .m programs which will need octave (or Matlab).
I understood, but I am talking of octave graphics interface
See also
https://octave.org/doc/v4.4.0/Graphics
place it now and not worry about this problem any more.
On 8 July 2018 at 09:36, Jon Turney wrote:
> On 06/07/2018 02:16, William Mitchell wrote:
>
>> I'm afraid that didn't help any. Now both glxinfo and octave print
>> nothing
>> and return to the shell promp
Yes, I use gnuplot and xmgrace in other situations. But here I have
several .m programs which will need octave (or Matlab).
On 6 July 2018 at 13:51, Marco Atzeri wrote:
> Am 26.06.2018 um 21:27 schrieb William Mitchell:
>
>> When I run octave on a fresh installation of cygwin64 on
On 06/07/2018 02:16, William Mitchell wrote:
I'm afraid that didn't help any. Now both glxinfo and octave print nothing
and return to the shell prompt almost immediately. For octave, this
includes no output when I run a .m script that usually prints quite a bit
before starting th
1 - 100 of 559 matches
Mail list logo
