help-octave
[Top][All Lists]
Advanced

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

installation errors of octave-forge parallel on windows


From: Hanan Rosemarin
Subject: installation errors of octave-forge parallel on windows
Date: Wed, 9 Apr 2014 03:24:20 +0300

hi

Installation of the parallel (required for the optim package) octave forge package on octave 3.8.1-1 (from http://mxeoctave.osuv.de/) on windows 7 generates the following errors.

>> pkg -forge install parallel
sclose.cc:37:24: fatal error: sys/socket.h: No such file or directory
 #include <sys/socket.h>
                        ^
compilation terminated.
sock-stream.cc: In function 'void handle_errno(std::string, int)':
sock-stream.cc:89:10: error: 'ETXTBSY' was not declared in this scope
     case ETXTBSY:
          ^
g++: error: sclose.o: No such file or directory
g++: error: sock-stream.o: No such file or directory
strip: 'sclose.oct': No such file
make: *** [sclose.oct] Error 1
make: Entering directory `/tmp/oct-2/parallel-2.2.0/src'
C:/Octave/Octave-3.8.1/bin/mkoctfile-3.8.1.exe -s sclose.cc sock-stream.cc
make: Leaving directory `/tmp/oct-2/parallel-2.2.0/src'

pkg: error running `make' for the parallel package.
error: called from 'configure_make' in file C:\Octave\Octave-3.8.1\share\octave\3.8.1\m\pkg\private\configur
e_make.m near line 82, column 9
error: called from:
error:   C:\Octave\Octave-3.8.1\share\octave\3.8.1\m\pkg\private\install.m at line 199, column 5
error:   C:\Octave\Octave-3.8.1\share\octave\3.8.1\m\pkg\pkg.m at line 394, column 9

the lack of socket.h support in MingW is well documented (e.g. http://stackoverflow.com/questions/1517762/sockets-in-mingwhttp://stackoverflow.com/questions/4638604/where-does-one-get-the-sys-socket-h-header-source-filehttp://sage.math.washington.edu/home/wstein/www/home/ericb/gnulib/lib/sys_socket.in.h).

The solution seems to range between modifying the forge package to include winsock2.h when compiling on windows to adding an alternate socket.h to MingW.

-
Hanan

reply via email to

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