Compiling Scilab 4.1.2
Michael
I'm really desperate. For 4 weeks I've been trying to compile scilab
4.1.2, but it doesn't work.
I'm working on windows xp. I bought Visual C++.net 2003, downloaded
Intel Fortran 9.1, downloaded Java J2SE JDK 5.0 and got the TCL/TK 8.4
prerequirements by Allan Cornet. And of course I have the source
files. I'm doing it like on this instruction on scilab.org: Compiling
scilab 4.x on windows....
I don't know why it does't work.
There are some errors when I try to compile Wscilex.exe:
fatal error LNK 1181: cannot open input file \scilab\bin\Atlas.lib
fatal error LNK 1181: cannot open input file \scilab\bin\arpack.lib
fatal error LNK 1104: cannot open input file \scilab\bin\LibScilab.lib
Do I need any other things to compile Scilab 4.1.2? Any other progs,
libraries etc.???
Best regards
Michael
Francois Vogel
> I'm working on windows xp. I bought Visual C++.net 2003, downloaded
> Intel Fortran 9.1,
From where?
> downloaded Java J2SE JDK 5.0 and got the TCL/TK 8.4
> prerequirements by Allan Cornet.
Do you have only the Tcl/Tk prerequirements, or the full
prerequirements? Where does what you have come from?
> And of course I have the source
> files. I'm doing it like on this instruction on scilab.org: Compiling
> scilab 4.x on windows....
Do you mean this page or what?
http://wiki.scilab.org/Compiling_Scilab_4.x_under_Windows
> I don't know why it does't work.
> There are some errors when I try to compile Wscilex.exe:
>
> fatal error LNK 1181: cannot open input file \scilab\bin\Atlas.lib
> fatal error LNK 1181: cannot open input file \scilab\bin\arpack.lib
> fatal error LNK 1104: cannot open input file \scilab\bin\LibScilab.lib
You seem to be missing some prerequirement files. They used to be
available on the Scilab website IIRC.
It was also possible to get them from their svn repository, but for me
at least this access is now closed (the password I had does no longer
work - why...?).
Note that a binary version of 4.1.2 is available however, why do you
want to compile it yourself? Also, there are more recent versions of
the 4.x tree out there: check out Scicoslab-4.3:
Francois
Michael
> Michael said on 20/11/2009 12:18:
>
> > I'm working on windows xp. I bought Visual C++.net 2003, downloaded
> > Intel Fortran 9.1,
>
> From where?
>
> > downloaded Java J2SE JDK 5.0 and got the TCL/TK 8.4
> > prerequirements by Allan Cornet.
>
> Do you have only the Tcl/Tk prerequirements, or the full
> prerequirements? Where does what you have come from?
>
> > And of course I have the source
>
> > files. I'm doing it like on this instruction on scilab.org: Compiling
> > scilab 4.x on windows....
>
>
> > I don't know why it does't work.
> > There are some errors when I try to compile Wscilex.exe:
>
> > fatal error LNK 1181: cannot open input file \scilab\bin\Atlas.lib
> > fatal error LNK 1181: cannot open input file \scilab\bin\arpack.lib
> > fatal error LNK 1104: cannot open input file \scilab\bin\LibScilab.lib
>
> You seem to be missing some prerequirement files. They used to be
> available on the Scilab website IIRC.
> It was also possible to get them from their svn repository, but for me
> at least this access is now closed (the password I had does no longer
> work - why...?).
>
> Note that a binary version of 4.1.2 is available however, why do you
> want to compile it yourself? Also, there are more recent versions of
> the 4.x tree out there: check out Scicoslab-4.3:
>
> http://www.scicoslab.org
>
Hi,
thanks for your answer. I'm studying mechanical engineering in Munich
and thats my diploma thesis. I have to change Scilab code so that the
real-time software TwinCAT (by Beckhoff in Germany) can import scicos-
block-diagrams. But first of all I have to get a compilable version.
My professor says it is better to take version 4.1.2 because of the
debugging function which doesn't work in newer versions of Scilab.
I don't know IIRC and scicoslab.org and Scilab version 4.3 either. I
thought 4.1.2 is the last of 4.x.
I got the files from svn://svn.scilab.org/scilab/tags/Scilab-412/Dev-Tools/tcltk/windows,
but since I didnt have the password I asked Allan Cornet from the
Scilab team and he sent me the files from the svn-link. I thought I
have all files together. But where are the missing files....
I bought Visual 2003 from ebay (a new product from Ireland) and Intel
fortran 9.1 from intel.com. But to download 9.1 is not that simple, so
there are instructions here: http://software.intel.com/en-us/articles/older-version-product/
I just want to compile any version, because I'm really getting crazy
because I've been trying it a long time now.
Regards Michael
Michael
>
> - Show quoted text -
Hi it's me again.
Is Scicoslab 4.3 easier to compile or maybe the instruction better?
Then I would try this version.
Are you able to compile it like it is described on scicoslab.org?
Michael
Michael
So I tried to follow the copilation instruction on scicoslab.org, but
I can't do it
cd /cygdrive/c/scicoslab/scilab
./autogen.sh --host=i686-pc-mingw32 --with-gfortran
There is no scilab folder in cd /cygdrive/c/scicoslab/
Are there some files missing?
Regards
Francois Vogel
> Is Scicoslab 4.3 easier to compile or maybe the instruction better?
> Then I would try this version.
>
> Are you able to compile it like it is described on scicoslab.org?
I'm part of the team that wrote them...
F.
Francois Vogel
>
> So I tried to follow the copilation instruction on scicoslab.org, but
> I can't do it
>
> cd /cygdrive/c/scicoslab/scilab
> ./autogen.sh --host=i686-pc-mingw32 --with-gfortran
>
> There is no scilab folder in cd /cygdrive/c/scicoslab/
Depends on what is the root tree where you installed ScicosLab sources.
What is the result (in cygwin) of
/cygdrive/c/scicoslab
?
Francois
Francois Vogel
> What is the result (in cygwin) of
>
> /cygdrive/c/scicoslab
Sorry, what is the result (the output in cygwin) of
ls /cygdrive/c/scicoslab
?
Francois
jpc
Hello Michael,
If you want to compile scicoslab on win32 you should
follow the compilation instructions which are given in the item
<<For Windows native win32 compilation with MinGW you can follow
Cygwin/Mingw Compilation.>>
Note that it should be better to get the source version on the git
server
since I am not sure that it will work with scicoslab-
gtk_4.3.orig.tar.gz (I haven't tested).
Regards
jpc
Michael
Hi,
thanks for the hint, I will try it.
Another problem is gcc-full-4.4.0-mingw32-bin-2.tar.lzma.
That file is corrupt, it can't be unzipped (untarred..).
So the problem is that installing MinGW 5.1 doesn't support fortran.
Thats why the commands
which gfortran and
gfortran --version
are not working.
Regards Michael
Francois Vogel
> Another problem is gcc-full-4.4.0-mingw32-bin-2.tar.lzma.
> That file is corrupt, it can't be unzipped (untarred..).
WFM. Try to download again.
Francois
Michael
Hi,
everything works now till that point: Configure and compile under
cygwin.
1. There is no c/scicoslab/scilab-folder
2. But I found the file autogen.sh in c/scicoslab
3. When I make the command:
./autogen.sh --host=i686-pc-mingw32 --with-gfortran
I get some failures:
./autogen.sh: line 3: $'r\': command not found
./autogen.sh: line 7: $'r\': command not found
./autogen.sh: line 9: $'r\': command not found
./autogen.sh: line 10: $'{r\': command not found
top-level package directory
: numeric argument required: 1
What's wrong there? Could you please help me?
Michel
Francois Vogel
> 3. When I make the command:
> ./autogen.sh --host=i686-pc-mingw32 --with-gfortran
> I get some failures:
>
> ./autogen.sh: line 3: $'r\': command not found
> ./autogen.sh: line 7: $'r\': command not found
> ./autogen.sh: line 9: $'r\': command not found
> ./autogen.sh: line 10: $'{r\': command not found
> top-level package directory
> : numeric argument required: 1
Looks like you edited autogen.sh in a windows editor.
autogen.sh is a file with linux line endings. If you edit it on
Windows with a low end editor this editor will most likely replace the
linux line endings by windows line endings without warning you (and it
may even do so completely silently, for instance autosaving the file).
Then when you try to run the file on linux (for you: in cygwin) you
get this kind of problems.
Try to get a clean copy of autogen.sh and of whatever file you edited.
Brute force approach: erase the contents of c:\scicoslab and get a
clean fresh copy of the git version from the Scicoslab website.
Francois
Michael
> On 24 nov, 09:09, Michael <mba...@t-online.de> wrote:
>
> > 3. When I make the command:
> > ./autogen.sh --host=i686-pc-mingw32 --with-gfortran
> > I get some failures:
>
> > ./autogen.sh: line 3: $'r\': command not found
> > ./autogen.sh: line 7: $'r\': command not found
> > ./autogen.sh: line 9: $'r\': command not found
> > ./autogen.sh: line 10: $'{r\': command not found
> > top-level package directory
> > : numeric argument required: 1
>
> Looks like you edited autogen.sh in a windows editor.
>
>
>
I cleaned the folder and downloaded it newly (of course also TCL
libraries), but it doesn't help.
The same failure as before.
Can try something else?
Francois Vogel
I can reproduce your problem when I edit autogen.sh in wordpad and
save it. This definitely looks like you have messed up the line
endings without noticing.
1. How *exactly* did you install cygwin? Did you change the default
options at install time, especially the settings for line endings?
These defaults should not be changed.
2. How *exactly* did you obtain the source code of Scicoslab? The
correct procedure is to run cygwin, and in the cygwin shell run the
following command:
git clone http://cermics.enpc.fr/~jpc/scilab-gtk-tiddly/scicoslab.git
Did you perhaps get the scicoslab source git version using a windows
git client instead? If so, you shouldn't do that but get the sources
from the cygwin shell.
Francois
Michael
No I didn't do that.
> 2. How *exactly* did you obtain the source code of Scicoslab? The
> correct procedure is to run cygwin, and in the cygwin shell run the
> following command:
> git clonehttp://cermics.enpc.fr/~jpc/scilab-gtk-tiddly/scicoslab.git
> Did you perhaps get the scicoslab source git version using a windows
> git client instead? If so, you shouldn't do that but get the sources
> from the cygwin shell.
>
Yes you're right. I used a windows GIT-client from the Scilab GIT
instruction, maybe thats the point! I didn't know that cygwin is able
to run GIT commands.
Thank you, I'll try this.
Jean-Pierre Vial
> On Nov 24, 4:05 pm, Francois Vogel <fsvogeln...@free.fr> wrote:
>> On 24 nov, 13:44, Michael <mba...@t-online.de> wrote:
>>
>>
>>
>>
>>
>>> On Nov 24, 10:38 am, Francois Vogel <fsvogeln...@free.fr> wrote:
>>>> On 24 nov, 09:09, Michael <mba...@t-online.de> wrote:
>>>>> 3. When I make the command:
>>>>> ./autogen.sh --host=i686-pc-mingw32 --with-gfortran
>>>>> I get some failures:
>>>>> ./autogen.sh: line 3: $'r\': command not found
>>>>> ./autogen.sh: line 7: $'r\': command not found
>>>>> ./autogen.sh: line 9: $'r\': command not found
>>>>> ./autogen.sh: line 10: $'{r\': command not found
>>>>> top-level package directory
>>>>> : numeric argument required: 1
>>>> Looks like you edited autogen.sh in a windows editor.
there is another way to get the same problem:
some windows unpackers (for decompacting zip or tgz files)
by default silently change the end of lines of the files
recognized as text files.
In that case, there are options (either command line options or
buttons in the graphical interface) to force so-called
binary unpacking
Michael
autogen.sh is working and also make all.
But the step after that
cp bin/cscilex.exe bin/scilex
make all
doesn't work, because there is neither cscilex.exe nor bin/scilex.
Does that mean that the cross compilation failed?
Do I have to unzip all files in Cygwin concerning your instruction?
Michael
Francois Vogel
> autogen.sh is working and also make all.
>
> But the step after that
>
> cp bin/cscilex.exe bin/scilex
> make all
>
> doesn't work, because there is neither cscilex.exe nor bin/scilex.
Well, what you're reporting is not consistent.
Either make all worked to its end and there is a cscilex.exe file in
the bin folder, or it did not work to the end and there is no such
file. Pick up your choice...
Francois
Michael
I dont know what went wrong and I unfortunately can't attach a
screenshot.
Francois Vogel
5a22b1d8-6aa2-404e...@m16g2000yqc.googlegroups.com...
> Well there is a Error 1 after make all.
> I dont know what went wrong and I unfortunately can't attach a
> screenshot.
Can't you just copy/paste the relevant part of the compilation output?
Anyway, I guess you should first check that there is absolutely no error
during the configure step first. Then try to understand why you have an
error at compile time. Most probably the error comes from a missing package
in cygwin.
Francois
Michael
I will prove that, but I don't think it comes from Cygwin because I
installed all available files.
Michael
p1output.c: In function `p1_const':
p1output.c:207: warning: long unsigned int format, tagptr arg (arg 5)
p1output.c:207: warning: long unsigned int format, tagptr arg (arg 5)
p1output.c: In function `p1_addr':
p1output.c:263: warning: suggest parentheses around && within ||
p1output.c:266: warning: suggest parentheses around && within ||
gcc -g -O2 -mieee-fp -Wall -c -o pread.o pread.c
pread.c: In function `readref':
pread.c:254: warning: suggest parentheses around && within ||
pread.c: In function `Pfile':
pread.c:892: warning: array subscript has type `char'
pread.c:894: warning: array subscript has type `char'
pread.c:897: warning: suggest parentheses around assignment used as
truth value
pread.c:907: warning: suggest parentheses around && within ||
pread.c:918: warning: suggest parentheses around assignment used as
truth value
pread.c: In function `read_Pfiles':
pread.c:960: warning: suggest parentheses around assignment used as
truth value
gcc -g -O2 -mieee-fp -Wall -c -o put.o put.c
put.c: In function `putconst':
put.c:379: warning: suggest parentheses around && within ||
put.c:276: warning: 'len' might be used uninitialized in this function
put.c:279: warning: 'nblanks' might be used uninitialized in this
function
put.c:280: warning: 'strp' might be used uninitialized in this
function
gcc -g -O2 -mieee-fp -Wall -c -o putpcc.o putpcc.c
putpcc.c: In function `putif':
putpcc.c:112: warning: suggest parentheses around assignment used as
truth value
putpcc.c: In function `putcx1':
putpcc.c:687: warning: suggest parentheses around assignment used as
truth value
putpcc.c:695: warning: array subscript has type `char'
putpcc.c:704: warning: array subscript has type `char'
putpcc.c:757: warning: suggest parentheses around assignment used as
truth value
putpcc.c:759: warning: suggest parentheses around assignment used as
truth value
putpcc.c: In function `putaddr':
putpcc.c:1193: warning: suggest explicit braces to avoid ambiguous
`else'
putpcc.c: In function `save_argtypes':
putpcc.c:1447: warning: suggest parentheses around assignment used as
truth valu
e
putpcc.c: In function `get_argtypes':
putpcc.c:1610: warning: unused variable `rp'
putpcc.c: In function `putcall':
putpcc.c:1751: warning: suggest parentheses around && within ||
putpcc.c: In function `get_argtypes':
putpcc.c:1607: warning: 'at0' might be used uninitialized in this
function
putpcc.c:1607: warning: 'at1' might be used uninitialized in this
function
putpcc.c:1613: warning: 'fname' might be used uninitialized in this
function
putpcc.c: In function `putcx1':
putpcc.c:669: warning: 'ltype' might be used uninitialized in this
function
putpcc.c:669: warning: 'rtype' might be used uninitialized in this
function
putpcc.c: In function `putx':
putpcc.c:533: warning: 'k' might be used uninitialized in this
function
putpcc.c: In function `putif':
putpcc.c:86: warning: 'where' might be used uninitialized in this
function
gcc -g -O2 -mieee-fp -Wall -c -o vax.o vax.c
vax.c: In function `count_args':
vax.c:223: warning: suggest parentheses around assignment used as
truth value
vax.c: In function `aawalk':
vax.c:249: warning: suggest parentheses around assignment used as
truth value
vax.c:251: warning: suggest parentheses around assignment used as
truth value
vax.c: In function `afwalk':
vax.c:280: warning: suggest parentheses around && within ||
vax.c: In function `prolog':
vax.c:447: warning: suggest parentheses around assignment used as
truth value
vax.c:492: warning: array subscript has type `char'
vax.c:493: warning: suggest explicit braces to avoid ambiguous `else'
gcc -g -O2 -mieee-fp -Wall -c -o formatdata.o formatdata.c
formatdata.c: In function `list_init_data':
formatdata.c:52: warning: suggest parentheses around assignment used
as truth va
lue
formatdata.c: In function `write_char_init':
formatdata.c:219: warning: suggest parentheses around assignment used
as truth v
alue
formatdata.c: In function `wr_one_init':
formatdata.c:391: warning: suggest explicit braces to avoid ambiguous
`else'
formatdata.c:276: warning: unused variable `datachar'
formatdata.c: In function `make_one_const':
formatdata.c:714: warning: suggest parentheses around assignment used
as truth v
alue
formatdata.c: In function `wr_equiv_init':
formatdata.c:979: warning: array subscript has type `char'
formatdata.c:996: warning: suggest parentheses around assignment used
as truth v
alue
formatdata.c: In function `wr_array_init':
formatdata.c:557: warning: 'k' might be used uninitialized in this
function
formatdata.c: In function `wr_equiv_init':
formatdata.c:947: warning: 'dL' might be used uninitialized in this
function
gcc -g -O2 -mieee-fp -Wall -c -o parse_args.o parse_args.c
parse_args.c: In function `lower_string':
parse_args.c:415: warning: suggest parentheses around assignment used
as truth v
alue
gcc -g -O2 -mieee-fp -Wall -c -o niceprintf.o niceprintf.c
niceprintf.c: In function `fwd_strcpy':
niceprintf.c:205: warning: suggest parentheses around assignment used
as truth v
alue
niceprintf.c: In function `adjust_pointer_in_string':
niceprintf.c:172: warning: 's0' might be used uninitialized in this
function
gcc -g -O2 -mieee-fp -Wall -c -o cds.o cds.c
cds.c: In function `cds':
cds.c:109: warning: suggest parentheses around assignment used as
truth value
gcc -g -O2 -mieee-fp -Wall -c -o sysdep.o sysdep.c
sysdep.c: In function `c_name':
sysdep.c:146: warning: suggest parentheses around assignment used as
truth value
sysdep.c: At top level:
sysdep.c:233: warning: return type defaults to `int'
sysdep.c: In function `fmt_init':
sysdep.c:373: warning: suggest parentheses around assignment used as
truth value
sysdep.c: At top level:
sysdep.c:439: warning: return type defaults to `int'
sysdep.c: In function `dsort':
sysdep.c:516: warning: suggest parentheses around assignment used as
truth value
gcc -g -O2 -mieee-fp -Wall -c -o version.o version.c
gcc -g -O2 -mieee-fp -Wall main.o init.o gram.o lex.o proc.o equiv.o
data.o fo
rmat.o expr.o exec.o intr.o io.o misc.o error.o mem.o names.o output.o
p1output.
o pread.o put.o putpcc.o vax.o formatdata.o parse_args.o niceprintf.o
cds.o sysd
ep.o version.o -o ../../../bin/f2c.exe
make[2]: Leaving directory `/cygdrive/c/scicoslab/routines/f2c/src'
make[1]: Leaving directory `/cygdrive/c/scicoslab/routines'
making all in pvm3...
make[1]: Entering directory `/cygdrive/c/scicoslab/pvm3'
making in . for MINGW
make[2]: Entering directory `/cygdrive/c/scicoslab/pvm3'
building in src
cd src; ../lib/aimk CC=gcc F77=gfortran install
making in MINGW/ for MINGW
make[3]: Entering directory `/cygdrive/c/scicoslab/pvm3/src/MINGW'
mkdir ../../lib/MINGW
compiling ddpro.c
../../src/ddpro.c: In function `hosterforkexec':
../../src/ddpro.c:1306: warning: passing arg 3 of `_spawnve' from
incompatible p
ointer type
../../src/ddpro.c:1306: warning: passing arg 4 of `_spawnve' from
incompatible p
ointer type
compiling host.c
compiling hoster-void.c
compiling imalloc.c
compiling msgbox.c
compiling pkt.c
compiling pmsg.c
compiling pvmalloc.c
compiling pvmcruft.c
compiling pvmd.c
compiling pvmdpack.c
compiling pvmdtev.c
compiling pvmerr.c
compiling pvmfrag.c
compiling pvmlog.c
compiling sdpro.c
compiling task.c
compiling tdpro.c
compiling waitc.c
compiling global.c
gcc -O -DCLUMP_ALLOC -DSTATISTICS -DTIMESTAMPLOG -DSANITY -I../../
include -DARCH
CLASS=\"MINGW\" -DIMA_MINGW -mno-cygwin -DHASSTDLIB -DWIN32 -
DSYSVBFUNC -DSYSVST
R -DHASERRORVARS -DNOWAIT3 -DNOGETDTBLSIZ -DNOUNIXDOM -DNOTMPNAM -
DMAXHOSTNAMELE
N=64 -DMAXPATHLEN=64 -DNEEDSFFS -Ic:/scicoslab/pvm3/include -Ic:/
scicoslab/pvm3/
tracer -Ic:/scicoslab/pvm3/src -c ../../xdr/xdr_mem.c
gcc -O -DCLUMP_ALLOC -DSTATISTICS -DTIMESTAMPLOG -DSANITY -I../../
include -DARCH
CLASS=\"MINGW\" -DIMA_MINGW -mno-cygwin -DHASSTDLIB -DWIN32 -
DSYSVBFUNC -DSYSVST
R -DHASERRORVARS -DNOWAIT3 -DNOGETDTBLSIZ -DNOUNIXDOM -DNOTMPNAM -
DMAXHOSTNAMELE
N=64 -DMAXPATHLEN=64 -DNEEDSFFS -Ic:/scicoslab/pvm3/include -Ic:/
scicoslab/pvm3/
tracer -Ic:/scicoslab/pvm3/src -c ../../src/../xdr/xdr_floa.c
gcc -O -DCLUMP_ALLOC -DSTATISTICS -DTIMESTAMPLOG -DSANITY -I../../
include -DARCH
CLASS=\"MINGW\" -DIMA_MINGW -mno-cygwin -DHASSTDLIB -DWIN32 -
DSYSVBFUNC -DSYSVST
R -DHASERRORVARS -DNOWAIT3 -DNOGETDTBLSIZ -DNOUNIXDOM -DNOTMPNAM -
DMAXHOSTNAMELE
N=64 -DMAXPATHLEN=64 -DNEEDSFFS -Ic:/scicoslab/pvm3/include -Ic:/
scicoslab/pvm3/
tracer -Ic:/scicoslab/pvm3/src -c ../../src/../xdr/xdr.c
gcc -O -DCLUMP_ALLOC -DSTATISTICS -DTIMESTAMPLOG -DSANITY -I../../
include -DARCH
CLASS=\"MINGW\" -DIMA_MINGW -mno-cygwin -DHASSTDLIB -DWIN32 -
DSYSVBFUNC -DSYSVST
R -DHASERRORVARS -DNOWAIT3 -DNOGETDTBLSIZ -DNOUNIXDOM -DNOTMPNAM -
DMAXHOSTNAMELE
N=64 -DMAXPATHLEN=64 -DNEEDSFFS -Ic:/scicoslab/pvm3/include -Ic:/
scicoslab/pvm3/
tracer -Ic:/scicoslab/pvm3/src -c ../pvmwin.c
gcc -O -DCLUMP_ALLOC -DSTATISTICS -DTIMESTAMPLOG -DSANITY -I../../
include -DARCH
CLASS=\"MINGW\" -DIMA_MINGW -mno-cygwin -DHASSTDLIB -DWIN32 -
DSYSVBFUNC -DSYSVST
R -DHASERRORVARS -DNOWAIT3 -DNOGETDTBLSIZ -DNOUNIXDOM -DNOTMPNAM -
DMAXHOSTNAMELE
N=64 -DMAXPATHLEN=64 -DNEEDSFFS -Ic:/scicoslab/pvm3/include -Ic:/
scicoslab/pvm3/
tracer -Ic:/scicoslab/pvm3/src -c ../regex/pvmregex.c -o
ming_pvmregex.o
../regex/pvmregex.c:41: warning: conflicting types for built-in
function 'malloc
'
gcc -O -DCLUMP_ALLOC -DSTATISTICS -DTIMESTAMPLOG -DSANITY -I../../
include -DARCH
CLASS=\"MINGW\" -DIMA_MINGW -mno-cygwin -DHASSTDLIB -DWIN32 -
DSYSVBFUNC -DSYSVST
R -DHASERRORVARS -DNOWAIT3 -DNOGETDTBLSIZ -DNOUNIXDOM -DNOTMPNAM -
DMAXHOSTNAMELE
N=64 -DMAXPATHLEN=64 -DNEEDSFFS -Ic:/scicoslab/pvm3/include -Ic:/
scicoslab/pvm3/
tracer -Ic:/scicoslab/pvm3/src -c ../regex/regex.c -o ming_regex.o
compiling pvmdabuf.c
compiling pvmdunix.c
cp pvmd3.exe ../../lib/MINGW
compiling tev.c
compiling lpvmcat.c
compiling lpvmgen.c
compiling lpvmpack.c
compiling lpvmglob.c
compiling lpvm.c
ranlib libpvm3.a
cp libpvm3.a ../../lib/MINGW
make[3]: Leaving directory `/cygdrive/c/scicoslab/pvm3/src/MINGW'
done building in src
building tracer
cd tracer; ../lib/aimk CC=gcc F77=gfortran install
making in MINGW/ for MINGW
make[3]: Entering directory `/cygdrive/c/scicoslab/pvm3/tracer/MINGW'
compiling tracer.c
compiling cmd.c
compiling trcglob.c
compiling trcmess.c
compiling trccompat.c
compiling trccompatglob.c
compiling trcutil.c
ranlib libpvmtrc.a
compiling trcsort.c
make[3]: Leaving directory `/cygdrive/c/scicoslab/pvm3/tracer/MINGW'
done building tracer
building console
cd console; ../lib/aimk CC=gcc F77=gfortran install
making in MINGW/ for MINGW
make[3]: Entering directory `/cygdrive/c/scicoslab/pvm3/console/MINGW'
compiling cons.c
compiling cmds.c
compiling job.c
compiling trc.c
linking pvm.exe
cp pvm.exe ../../lib/MINGW
make[3]: Leaving directory `/cygdrive/c/scicoslab/pvm3/console/MINGW'
done building console
building group server and library
cd pvmgs; ../lib/aimk CC=gcc F77=gfortran install
making in MINGW/ for MINGW
make[3]: Entering directory `/cygdrive/c/scicoslab/pvm3/pvmgs/MINGW'
mkdir ../../bin
mkdir: cannot create directory `../../bin': File exists
make[3]: [../../bin/MINGW] Error 1 (ignored)
mkdir ../../bin/MINGW
compiling pvm_gstat.c
compiling pvmgsu_core.c
compiling pvmgsu_aux.c
compiling pvmgs_func.c
ranlib libgpvm3.a
linking pvm_gstat.exe
cp pvm_gstat.exe ../../bin/MINGW
compiling pvmgs_core.c
linking pvmgs.exe
cp pvmgs.exe ../../bin/MINGW
compiling pvmgroups.c
linking pvmgroups.exe
cp pvmgroups.exe ../../bin/MINGW
cp libgpvm3.a ../../lib/MINGW
ranlib ../../lib/MINGW/libgpvm3.a
cp pvmgs.exe ../../lib/MINGW
make[3]: Leaving directory `/cygdrive/c/scicoslab/pvm3/pvmgs/MINGW'
done building group server and library
building hoster
cd hoster; ../lib/aimk CC=gcc F77=gfortran install
making in MINGW/ for MINGW
make[3]: Entering directory `/cygdrive/c/scicoslab/pvm3/hoster/MINGW'
gcc -O -I../../include -I../../src -DIMA_MINGW -mno-cygwin -DHASSTDLIB
-DWIN32 -
DSYSVBFUNC -DSYSVSTR -DHASERRORVARS -DNOWAIT3 -DNOGETDTBLSIZ -
DNOUNIXDOM -DNOTMP
NAM -DMAXHOSTNAMELEN=64 -DMAXPATHLEN=64 -DNEEDSFFS -Ic:/scicoslab/pvm3/
include -
Ic:/scicoslab/pvm3/tracer -Ic:/scicoslab/pvm3/src -c ../pvmwinrexec.c
../pvmwinrexec.c: In function `PassOutput':
../pvmwinrexec.c:202: warning: passing arg 1 of `_beginthread' from
incompatible
pointer type
../pvmwinrexec.c: In function `PassError':
../pvmwinrexec.c:262: warning: passing arg 1 of `_beginthread' from
incompatible
pointer type
gcc -O -I../../include -I../../src -DIMA_MINGW -mno-cygwin -DHASSTDLIB
-DWIN32 -
DSYSVBFUNC -DSYSVSTR -DHASERRORVARS -DNOWAIT3 -DNOGETDTBLSIZ -
DNOUNIXDOM -DNOTMP
NAM -DMAXHOSTNAMELEN=64 -DMAXPATHLEN=64 -DNEEDSFFS -Ic:/scicoslab/pvm3/
include -
Ic:/scicoslab/pvm3/tracer -Ic:/scicoslab/pvm3/src -c ../pvmwinrsh.c
gcc -O -I../../include -I../../src -DIMA_MINGW -mno-cygwin -DHASSTDLIB
-DWIN32 -
DSYSVBFUNC -DSYSVSTR -DHASERRORVARS -DNOWAIT3 -DNOGETDTBLSIZ -
DNOUNIXDOM -DNOTMP
NAM -DMAXHOSTNAMELEN=64 -DMAXPATHLEN=64 -DNEEDSFFS -Ic:/scicoslab/pvm3/
include -
Ic:/scicoslab/pvm3/tracer -Ic:/scicoslab/pvm3/src -o hoster.exe ../../
hoster/hos
ter.c pvmwinrexec.o pvmwinrsh.o -L../../lib/MINGW -lpvm3 -mwindows -
lwsock32 -lk
ernel32 -lgdi32 -lwinspool -lcomdlg32 -ladvapi32 -lshell32 -lole32 -
loleaut32 -
luuid -lm
cp hoster.exe ../../bin/MINGW
make[3]: Leaving directory `/cygdrive/c/scicoslab/pvm3/hoster/MINGW'
done building hoster
make[2]: Leaving directory `/cygdrive/c/scicoslab/pvm3'
make[1]: Leaving directory `/cygdrive/c/scicoslab/pvm3'
creation of bin/LibScilab.dll ...gcc: routines/wsci/Rscilab.o: No such
file or d
irectory
gcc: c:/scicoslab/libs/scicos.a: No such file or directory
gcc: c:/scicoslab/libs/os_specific.a: No such file or directory
gcc: c:/scicoslab/libs/wsci.a: No such file or directory
gcc: c:/scicoslab/libs/graphics.a: No such file or directory
gcc: c:/scicoslab/libs/menusX.a: No such file or directory
make: *** [shared-win32] Error 1
Michael Bajer@MichaelBajer-PC /cygdrive/c/scicoslab
$ cp bin/cscilex.exe bin/scilex
cp: cannot stat `bin/cscilex.exe': No such file or directory
Francois Vogel
> make[1]: Leaving directory `/cygdrive/c/scicoslab/pvm3'
> creation of bin/LibScilab.dll ...gcc: routines/wsci/Rscilab.o: No such
> file or directory
> gcc: c:/scicoslab/libs/scicos.a: No such file or directory
> gcc: c:/scicoslab/libs/os_specific.a: No such file or directory
> gcc: c:/scicoslab/libs/wsci.a: No such file or directory
> gcc: c:/scicoslab/libs/graphics.a: No such file or directory
> gcc: c:/scicoslab/libs/menusX.a: No such file or directory
> make: *** [shared-win32] Error 1
It's wrong way before the small part of output you have provided. A
number of files are not created by the build process.
Can't help you at this point, because you do not provide the relevant
part of the output.
First of all, are you really 100% sure that the autogen/configure step
has absolutely no error? You can post the output here.
Francois
Michael
> has absolutely no error? You can post the output here.
>
I can't detect an error in the configuration log-file.
Here is the log of the autogen.sh-configuration:
user@user-pc/cygdrive/c/scicoslab
$ ./autogen.sh --host=i686-pc-mingw32 --with-gfortran
processing .
Running libtoolize --force --copy
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config'.
libtoolize: copying file `config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `config'.
libtoolize: copying file `config/libtool.m4'
libtoolize: copying file `config/ltoptions.m4'
libtoolize: copying file `config/ltsugar.m4'
libtoolize: copying file `config/ltversion.m4'
libtoolize: copying file `config/lt~obsolete.m4'
libtoolize: Consider adding `-I config' to ACLOCAL_AMFLAGS in
Makefile.am.
libtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT'
Running aclocal -I config ...
Running autoheader...
Running automake --gnu ...
configure.in:13: installing `config/missing'
automake-1.11: no `Makefile.am' found for any configure output
Running autoconf ...
Running ./configure --host=i686-pc-mingw32 --with-gfortran ...
configure: WARNING: If you wanted to set the --build type, don't use --
host.
If a cross compiler is detected then cross compile mode will be
used.
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for i686-pc-mingw32-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-mingw32
creating Path.incl
checking for gfortran... yes
checking for i686-pc-mingw32-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking for i686-pc-mingw32-g++... no
checking for i686-pc-mingw32-c++... no
checking for i686-pc-mingw32-gpp... no
checking for i686-pc-mingw32-aCC... no
checking for i686-pc-mingw32-CC... no
checking for i686-pc-mingw32-cxx... no
checking for i686-pc-mingw32-cc++... no
checking for i686-pc-mingw32-cl.exe... no
checking for i686-pc-mingw32-FCC... no
checking for i686-pc-mingw32-KCC... no
checking for i686-pc-mingw32-RCC... no
checking for i686-pc-mingw32-xlC_r... no
checking for i686-pc-mingw32-xlC... no
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... none
checking for i686-pc-mingw32-g77... no
checking for i686-pc-mingw32-xlf... no
checking for i686-pc-mingw32-f77... no
checking for i686-pc-mingw32-frt... no
checking for i686-pc-mingw32-pgf77... no
checking for i686-pc-mingw32-cf77... no
checking for i686-pc-mingw32-fort77... no
checking for i686-pc-mingw32-fl32... no
checking for i686-pc-mingw32-af77... no
checking for i686-pc-mingw32-xlf90... no
checking for i686-pc-mingw32-f90... no
checking for i686-pc-mingw32-pgf90... no
checking for i686-pc-mingw32-pghpf... no
checking for i686-pc-mingw32-epcf90... no
checking for i686-pc-mingw32-gfortran... no
checking for i686-pc-mingw32-g95... no
checking for i686-pc-mingw32-xlf95... no
checking for i686-pc-mingw32-f95... no
checking for i686-pc-mingw32-fort... no
checking for i686-pc-mingw32-ifort... no
checking for i686-pc-mingw32-ifc... no
checking for i686-pc-mingw32-efc... no
checking for i686-pc-mingw32-pgf95... no
checking for i686-pc-mingw32-lf95... no
checking for i686-pc-mingw32-ftn... no
checking for g77... g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether g77 accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking whether ln -s works... yes
checking for i686-pc-mingw32-ranlib... no
checking for ranlib... ranlib
checking for i686-pc-mingw32-ar... no
checking for ar... ar
checking how to get verbose linking output from g77... -v
checking for Fortran 77 libraries of g77... -L/usr/lib/gcc/i686-pc-
cygwin/3.4.4
-L/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../.. -lfrtbegin -lg2c -
lcygwin -luser32
-lkernel32 -ladvapi32 -lshell32
checking for IEEE compiler flags... none
checking for main in -lieee... no
configuration of libtool
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/i686-pc-cygwin/bin/ld.exe
checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld...
yes
checking for BSD- or MS-compatible name lister (nm)... no
checking for i686-pc-mingw32-dumpbin... no
checking for i686-pc-mingw32-link... no
checking for dumpbin... no
checking for link... link -dump
checking the name lister (nm) interface... BSD nm
checking the maximum length of command line arguments... 8192
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert i686-pc-cygwin paths to i686-pc-mingw32
format... func_c
ygwin_to_mingw_path_convert
checking for /usr/i686-pc-cygwin/bin/ld.exe option to reload object
files... -r
checking for i686-pc-mingw32-objdump... no
checking for objdump... objdump
checking how to recognize dependent libraries... file_magic ^x86
archive import|
^x86 DLL
checking for i686-pc-mingw32-dlltool... no
checking for dlltool... dlltool
checking how to associate runtime and link libraries...
func_cygming_dll_for_imp
lib_fallback
checking for i686-pc-mingw32-ar... ar
checking for i686-pc-mingw32-strip... strip
checking for i686-pc-mingw32-ranlib... ranlib
checking command to parse nm output from gcc object... ok
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -DDLL_EXPORT -DPIC
checking if gcc PIC flag -DDLL_EXPORT -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/i686-pc-cygwin/bin/ld.exe)
supports shared
libraries... yes
checking whether -lc should be explicitly linked in... yes
checking dynamic linker characteristics... Win32 ld.exe
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/i686-pc-cygwin/bin/ld.exe
checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld...
yes
checking whether the g++ linker (/usr/i686-pc-cygwin/bin/ld.exe)
supports shared
libraries... yes
checking for g++ option to produce PIC... -DDLL_EXPORT -DPIC
checking if g++ PIC flag -DDLL_EXPORT -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/i686-pc-cygwin/bin/ld.exe)
supports shared
libraries... yes
checking dynamic linker characteristics... Win32 ld.exe
checking how to hardcode library paths into programs... immediate
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for gfortran option to produce PIC... -DDLL_EXPORT
checking if gfortran PIC flag -DDLL_EXPORT works... yes
checking if gfortran static flag -static works... yes
checking if gfortran supports -c -o file.o... yes
checking if gfortran supports -c -o file.o... (cached) yes
checking whether the gfortran linker (/usr/i686-pc-cygwin/bin/ld.exe)
supports s
hared libraries... yes
checking dynamic linker characteristics... Win32 ld.exe
checking how to hardcode library paths into programs... immediate
end of configuration of libtool
checking if iargc name in Fortran library is _gfortran_iargc... yes
checking for leading and/or trailing underscores... yes yes
checking for use of sharpsign in CPP... yes
checking for main in -lm... yes
checking for exp10... no
checking for getwd... yes
checking for sleep... yes
checking for strerror... yes
checking for usleep... yes
checking for finite... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking values.h usability... no
checking values.h presence... no
checking for values.h... no
checking for main in -lncurses... yes
checking for PVM architecture... CYGWIN
configure: WARNING: checking for tcl/tk.
checking for Tcl configuration... found /usr/lib/tclConfig.sh
checking for existence of /usr/lib/tclConfig.sh... loading
checking for Tk configuration... found /usr/lib/tkConfig.sh
checking for existence of /usr/lib/tkConfig.sh... loading
checking if tcl is version 8.4 or later... yes
checking if tcl is version 8.4 or later... yes
checking for ocamlc... yes
checking for ocamlopt... yes
checking for ocamldep... yes
checking expat.h usability... yes
checking expat.h presence... yes
checking for expat.h... yes
checking for XML_ParserCreate in -lexpat... yes
checking for xsltproc... yes
configure: WARNING: cannot check for man
configure: creating ./config.status
config.status: WARNING: 'config/configuration.in' seems to ignore the
--dataroo
tdir setting
config.status: creating config/Makefile.aix
config.status: creating config/Makefile.ultrix
config.status: creating config/Makeso.incl
config.status: creating config/Version.incl
config.status: creating imp/Makefile
config.status: creating examples/Makefile
config.status: creating macros/util/browsehelp.sci
config.status: creating macros/util/gettklib.sci
config.status: creating macros/util/gettkversion.sci
config.status: creating macros/util/ilib_unix_soname.sci
config.status: creating macros/util/xmlfiletohtml.sci
config.status: creating pvm3/Makefile
config.status: creating pvm3/Makefile.aimk
config.status: creating pvm3/hoster/Makefile.aimk
config.status: creating routines/Makefile
config.status: creating routines/version.h
config.status: creating routines/calelm/Makefile
config.status: creating routines/control/Makefile
config.status: creating routines/default/Makefile
config.status: creating routines/expatsci/Makefile
config.status: creating routines/graphics/Makefile
config.status: creating routines/gtksci/Makefile
config.status: creating routines/gzvt2/Makefile
config.status: creating routines/interf/Makefile
config.status: creating routines/Javasci/Makelib
config.status: creating routines/lapack/Makefile
config.status: creating routines/menusX/Makefile
config.status: creating routines/os_specific/Makefile
config.status: creating routines/optim/Makefile
config.status: creating routines/poly/Makefile
config.status: creating routines/sparse/Makefile
config.status: creating routines/system/Makefile
config.status: creating routines/system/banier.c
config.status: creating routines/system2/Makefile
config.status: creating routines/xsci/Makefile
config.status: creating scripts/Makefile
config.status: creating scripts/scilab.g
config.status: creating scripts/scilab-gtk.g
config.status: creating routines/config.h
config.status: executing depfiles commands
config.status: executing libtool commands
*******************
* Summary *
*******************
Managed by pkg-config..:
Lapack and Blas........:
Terminal...............: -lncurses
C compiler.............: gcc
C options..............: -g -O2 -mieee-fp -Wall
Fortran compiler.......: gfortran
Fortran options........: -g -O2 -Wall -Wno-unused -Wno-uninitialized
Now type `make' to compile.
Francois Vogel
> checking for g77... g77
> checking whether we are using the GNU Fortran 77 compiler... yes
> checking whether g77 accepts -g... yes
> checking how to run the C preprocessor... gcc -E
> checking whether ln -s works... yes
> checking for i686-pc-mingw32-ranlib... no
> checking for ranlib... ranlib
> checking for i686-pc-mingw32-ar... no
> checking for ar... ar
> checking how to get verbose linking output from g77... -v
> checking for Fortran 77 libraries of g77... -L/usr/lib/gcc/i686-pc-
> cygwin/3.4.4
> -L/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../.. -lfrtbegin -lg2c -
> lcygwin -luser32
> -lkernel32 -ladvapi32 -lshell32
It looks like g77 is used instead of gfortran, which should not be the
case.
> checking for ld used by gcc... /usr/i686-pc-cygwin/bin/ld.exe
> checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld...
> yes
If you have followed the instructions on the Scicoslab website I think
you should have ld from the mingw folder instead, i.e.:
checking for ld used by gcc... c:/mingw/mingw32/bin/ld.exe
checking if the linker (c:/mingw/mingw32/bin/ld.exe) is GNU ld... yes
Overall it seems that you're not using the binaries from mingw (did
you really install mingw and its compilers?), and since you have
installed a full cygwin, the cygwin binaries are used.
Francois