octave-maintainers
[Top][All Lists]
Advanced

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

Re: who is building Octave on Windows systems?


From: Benjamin Lindner
Subject: Re: who is building Octave on Windows systems?
Date: Tue, 25 Jan 2011 16:44:54 +0100

>> Is anyone other than Tatsuro building Octave on Windows systems?

I am also (after quite some time offline) again building for windows.

> From the ML repository, Ole Jacob Hagen built the octave.
> He suggest that the removal of gnulib name space from unlink,
>
> http://octave.1599824.n4.nabble.com/MinGW-compile-problems-td2251930.html
>
> Of course Benjamin Lindner, who has been a maintainer of the binary 
> distribution of octave for verion
> 3.0 and 3.2.
>
> He seems to have been too busy to commit build activity but seems to restart 
> commitment on the ML.
> I hope he will see this post and will commit to these issues.

seen it.

>> has reported a few build problems, but no one has confirmed them:
>>
>>   https://savannah.gnu.org/bugs/?32192
>>   https://savannah.gnu.org/bugs/?32200

I can confirm both of them.

The workaround is to include <unistd.h> from gnulib *twice*:

diff --git a/liboctave/oct-env.cc b/liboctave/oct-env.cc
--- a/liboctave/oct-env.cc
+++ b/liboctave/oct-env.cc
@@ -48,6 +48,7 @@

 #include <sys/types.h>
 #include <unistd.h>
+#include <unistd.h>

 #include "progname.h"

diff --git a/src/oct-hist.cc b/src/oct-hist.cc
--- a/src/oct-hist.cc
+++ b/src/oct-hist.cc
@@ -44,6 +44,7 @@

 #include <sys/types.h>
 #include <unistd.h>
+#include <unistd.h>

 #include "cmd-hist.h"
 #include "file-ops.h"


This doesn't fix the original problem, though.
And I haven't got down to the actual problem here. Gnulib's headers
are hard to read with their phletora of if-else clauses...

I am running a fresh build with updated gnulib source at the moment.
Let's see if I can debug this further.

benjamin


reply via email to

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