<div dir="ltr">I'm sorry, I will.<br><br><div class="gmail_quote">On Thu, Mar 29, 2012 at 10:52 PM, Sylvestre Ledru <span dir="ltr"><<a href="mailto:sylvestre.ledru@scilab-enterprises.com">sylvestre.ledru@scilab-enterprises.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div text="#000000" bgcolor="#ffffff">
Please switch to the arpack-ng mailing or, at least, on the
Scilab-dev mailing list. It is clearly not related to Scilab user
issues.<div><div></div><div class="h5"><br>
<br>
On 29/03/2012 19:18, Sumeet wrote:
<blockquote type="cite">
<div dir="ltr">Thanks Sylvestre and Charlie.
<div><br>
</div>
<div>I was getting an error in spite of having the fortran
compiler installed. I tried removing the fortran77-compiler
and having only gfortran-4.4, but then ./configure returns an
error. So apparently, fortran77 is a must. I'll look into
removing the -g flag.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Sumeet.</div>
<div><br>
</div>
<div>In case this helps, here's the ./configure output on
removing fortran77-compiler:</div>
<blockquote style="margin:0pt 0pt 0pt 40px;border:medium none;padding:0px">
<div>
<div>checking for a BSD-compatible install...
/usr/bin/install -c</div>
</div>
<div>
<div>checking whether build environment is sane... yes</div>
</div>
<div>
<div>checking for a thread-safe mkdir -p... /bin/mkdir -p</div>
</div>
<div>
<div>checking for gawk... gawk</div>
</div>
<div>
<div>checking whether make sets $(MAKE)... yes</div>
</div>
<div>
<div>checking for g77... no</div>
</div>
<div>
<div>checking for xlf... no</div>
</div>
<div>
<div>checking for f77... no</div>
</div>
<div>
<div>checking for frt... no</div>
</div>
<div>
<div>checking for pgf77... no</div>
</div>
<div>
<div>checking for cf77... no</div>
</div>
<div>
<div>checking for fort77... no</div>
</div>
<div>
<div>checking for fl32... no</div>
</div>
<div>
<div>checking for af77... no</div>
</div>
<div>
<div>checking for xlf90... no</div>
</div>
<div>
<div>checking for f90... no</div>
</div>
<div>
<div>checking for pgf90... no</div>
</div>
<div>
<div>checking for pghpf... no</div>
</div>
<div>
<div>checking for epcf90... no</div>
</div>
<div>
<div>checking for gfortran... no</div>
</div>
<div>
<div>checking for g95... no</div>
</div>
<div>
<div>checking for xlf95... no</div>
</div>
<div>
<div>checking for f95... no</div>
</div>
<div>
<div>checking for fort... no</div>
</div>
<div>
<div>checking for ifort... no</div>
</div>
<div>
<div>checking for ifc... no</div>
</div>
<div>
<div>checking for efc... no</div>
</div>
<div>
<div>checking for pgf95... no</div>
</div>
<div>
<div>checking for lf95... no</div>
</div>
<div>
<div>checking for ftn... no</div>
</div>
<div>
<div>checking whether the Fortran 77 compiler works... no</div>
</div>
<div>
<div>configure: error: in
`/home/sumeet/Downloads/arpack-ng':</div>
</div>
<div>
<div>configure: error: Fortran 77 compiler cannot create
executables</div>
</div>
<div>
<div>See `config.log' for more details.</div>
</div>
</blockquote>
<div><br>
</div>
<div>Here's the ./configure output with fortran77-compiler
present:</div>
<blockquote style="margin:0pt 0pt 0pt 40px;border:medium none;padding:0px">
<div>
<div>checking for a BSD-compatible install...
/usr/bin/install -c</div>
<div>checking whether build environment is sane... yes</div>
<div>checking for a thread-safe mkdir -p... /bin/mkdir -p</div>
<div>checking for gawk... gawk</div>
<div>checking whether make sets $(MAKE)... yes</div>
<div>checking for g77... no</div>
<div>checking for xlf... no</div>
<div>checking for f77... f77</div>
<div>checking whether the Fortran 77 compiler works... yes</div>
<div>checking for Fortran 77 compiler default output file
name... a.out</div>
<div>checking for suffix of executables... </div>
<div>checking whether we are cross compiling... no</div>
<div>checking for suffix of object files... o</div>
<div>checking whether we are using the GNU Fortran 77
compiler... yes</div>
<div>checking whether f77 accepts -g... yes</div>
<div>checking build system type... i686-pc-linux-gnu</div>
<div>checking host system type... i686-pc-linux-gnu</div>
<div>checking how to print strings... printf</div>
<div>checking for style of include used by make... GNU</div>
<div>checking for gcc... gcc</div>
<div>checking whether we are using the GNU C compiler... yes</div>
<div>checking whether gcc accepts -g... yes</div>
<div>checking for gcc option to accept ISO C89... none
needed</div>
<div>checking dependency style of gcc... none</div>
<div>checking for a sed that does not truncate output...
/bin/sed</div>
<div>checking for grep that handles long lines and -e...
/bin/grep</div>
<div>checking for egrep... /bin/grep -E</div>
<div>checking for fgrep... /bin/grep -F</div>
<div>checking for ld used by gcc... /usr/bin/ld</div>
<div>checking if the linker (/usr/bin/ld) is GNU ld... yes</div>
<div>checking for BSD- or MS-compatible name lister (nm)...
/usr/bin/nm -B</div>
<div>checking the name lister (/usr/bin/nm -B) interface...
BSD nm</div>
<div>checking whether ln -s works... yes</div>
<div>checking the maximum length of command line
arguments... 1572864</div>
<div>checking whether the shell understands some XSI
constructs... yes</div>
<div>checking whether the shell understands "+="... yes</div>
<div>checking how to convert i686-pc-linux-gnu file names to
i686-pc-linux-gnu format... func_convert_file_noop</div>
<div>checking how to convert i686-pc-linux-gnu file names to
toolchain format... func_convert_file_noop</div>
<div>checking for /usr/bin/ld option to reload object
files... -r</div>
<div>checking for objdump... objdump</div>
<div>checking how to recognize dependent libraries...
pass_all</div>
<div>checking for dlltool... no</div>
<div>
checking how to associate runtime and link libraries...
printf %s\n</div>
<div>checking for ar... ar</div>
<div>checking for archiver @FILE support... @</div>
<div>checking for strip... strip</div>
<div>checking for ranlib... ranlib</div>
<div>checking command to parse /usr/bin/nm -B output from
gcc object... ok</div>
<div>checking for sysroot... no</div>
<div>checking for mt... mt</div>
<div>checking if mt is a manifest tool... no</div>
<div>checking how to run the C preprocessor... gcc -E</div>
<div>checking for ANSI C header files... yes</div>
<div>checking for sys/types.h... yes</div>
<div>checking for sys/stat.h... yes</div>
<div>checking for stdlib.h... yes</div>
<div>checking for string.h... yes</div>
<div>checking for memory.h... yes</div>
<div>checking for strings.h... yes</div>
<div>checking for inttypes.h... yes</div>
<div>checking for stdint.h... yes</div>
<div>checking for unistd.h... yes</div>
<div>checking for dlfcn.h... yes</div>
<div>checking for objdir... .libs</div>
<div>checking if gcc supports -fno-rtti -fno-exceptions...
no</div>
<div>checking for gcc option to produce PIC... -fPIC -DPIC</div>
<div>checking if gcc PIC flag -fPIC -DPIC works... yes</div>
<div>checking if gcc static flag -static works... yes</div>
<div>checking if gcc supports -c -o file.o... yes</div>
<div>checking if gcc supports -c -o file.o... (cached) yes</div>
<div>checking whether the gcc linker (/usr/bin/ld) supports
shared libraries... yes</div>
<div>checking whether -lc should be explicitly linked in...
no</div>
<div>checking dynamic linker characteristics... GNU/Linux
ld.so</div>
<div>checking how to hardcode library paths into programs...
immediate</div>
<div>checking whether stripping libraries is possible... yes</div>
<div>checking if libtool supports shared libraries... yes</div>
<div>checking whether to build shared libraries... yes</div>
<div>checking whether to build static libraries... yes</div>
<div>checking if libtool supports shared libraries... yes</div>
<div>checking whether to build shared libraries... yes</div>
<div>checking whether to build static libraries... yes</div>
<div>checking for f77 option to produce PIC... -fPIC</div>
<div>checking if f77 PIC flag -fPIC works... yes</div>
<div>checking if f77 static flag -static works... yes</div>
<div>checking if f77 supports -c -o file.o... yes</div>
<div>checking if f77 supports -c -o file.o... (cached) yes</div>
<div>checking whether the f77 linker (/usr/bin/ld) supports
shared libraries... yes</div>
<div>checking dynamic linker characteristics... (cached)
GNU/Linux ld.so</div>
<div>checking how to hardcode library paths into programs...
immediate</div>
<div>checking how to get verbose linking output from f77...
configure: WARNING: cannot determine how to obtain linking
information from f77</div>
<div><br>
</div>
<div>checking for Fortran 77 libraries of f77... </div>
<div>checking for dummy main to link with Fortran 77
libraries... none</div>
<div>checking for Fortran 77 name-mangling scheme... lower
case, underscore, extra underscore</div>
<div>checking if sgemm_ is being linked in already... no</div>
<div>checking for ATL_xerbla in -latlas... no</div>
<div>checking for sgemm_ in -lblas... yes</div>
<div>checking for dgemm_ in -ldgemm... no</div>
<div>checking for sgemm_ in -lmkl... no</div>
<div>checking for sgemm_ in -framework vecLib... no</div>
<div>checking for sgemm_ in -lcxml... no</div>
<div>checking for sgemm_ in -ldxml... no</div>
<div>checking for sgemm_ in -lscs... no</div>
<div>checking for sgemm_ in -lcomplib.sgimath... no</div>
<div>checking for sgemm_ in -lblas... (cached) yes</div>
<div>checking for sgemm_ in -lessl... no</div>
<div>checking for sgemm_ in -lblas... (cached) yes</div>
<div>checking for cheev_... no</div>
<div>checking for cheev_ in -llapack... yes</div>
<div>checking for MPI mode... configure: creating
./config.status</div>
<div>config.status: creating Makefile</div>
<div>config.status: creating SRC/Makefile</div>
<div>config.status: creating UTIL/Makefile</div>
<div>config.status: creating TESTS/Makefile</div>
<div>config.status: creating PARPACK/Makefile</div>
<div>config.status: creating PARPACK/SRC/Makefile</div>
<div>config.status: creating PARPACK/SRC/MPI/Makefile</div>
<div>config.status: creating PARPACK/UTIL/Makefile</div>
<div>config.status: creating PARPACK/UTIL/MPI/Makefile</div>
<div>config.status: executing depfiles commands</div>
<div>config.status: executing libtool commands</div>
</div>
</blockquote>
<div><br>
<div class="gmail_quote">On Thu, Mar 29, 2012 at 10:20 PM,
Charles Warner <span dir="ltr"><<a href="mailto:cwarner.cw711@gmail.com" target="_blank">cwarner.cw711@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Two comments on your error message:
your make file is trying to run libtool with a "-g"
option, which libtool does not recognize. I am not sure
what the "-g" option is intended to provide, but you might
try editing the make file and eliminating this option on
the calling line.
<div>
Next, why are you using Fortran77 rather than gfortran?
Is this a requirement of the arpack-ng package? If so,
it is an indication that it is built on pretty old
technology...Some Fortran77 features do not compile well
on newer systems.</div>
<div><br>
</div>
<div>Charlie
<div>
<div><br>
<br>
<div class="gmail_quote">On Thu, Mar 29, 2012 at
11:27 AM, Sylvestre Ledru <span dir="ltr"><<a href="mailto:sylvestre.ledru@scilab-enterprises.com" target="_blank">sylvestre.ledru@scilab-enterprises.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div text="#000000" bgcolor="#ffffff">
<div>
<div> On 29/03/2012 18:23, Sumeet wrote:
<blockquote type="cite">
<div dir="ltr">Hi,
<div><br>
</div>
<div>I'm trying to compile arpack-ng
on Ubuntu 10.04 (in order to build
Scilab nightly build), using the
standard ./configure, make, make
install method.</div>
<div><br>
</div>
<div>I get the following error:</div>
<div><br>
</div>
<blockquote style="margin:0pt 0pt 0pt 40px;border:medium none;padding:0px">
<div>
<div>Making install in PARPACK</div>
</div>
<div>
<div>make[1]: Entering directory
`/home/sumeet/Downloads/arpack-ng/PARPACK'</div>
</div>
<div>
<div>Making install in UTIL</div>
</div>
<div>
<div>make[2]: Entering directory
`/home/sumeet/Downloads/arpack-ng/PARPACK/UTIL'</div>
</div>
<div>
<div>Making install in MPI</div>
</div>
<div>
<div>make[3]: Entering directory
`/home/sumeet/Downloads/arpack-ng/PARPACK/UTIL/MPI'</div>
</div>
<div>
<div>/bin/bash ../../../libtool
--tag=F77 --mode=compile -g
-O2 -c -o pivout.lo pivout.f</div>
</div>
<div>
<div>libtool: compile:
unrecognized option `-g'</div>
</div>
<div>
<div>libtool: compile: Try
`libtool --help' for more
information.</div>
</div>
<div>
<div>make[3]: *** [pivout.lo]
Error 1</div>
</div>
<div>
<div>make[3]: Leaving directory
`/home/sumeet/Downloads/arpack-ng/PARPACK/UTIL/MPI'</div>
</div>
<div>
<div>make[2]: ***
[install-recursive] Error 1</div>
</div>
<div>
<div>make[2]: Leaving directory
`/home/sumeet/Downloads/arpack-ng/PARPACK/UTIL'</div>
</div>
<div>
<div>make[1]: ***
[install-recursive] Error 1</div>
</div>
<div>
<div>make[1]: Leaving directory
`/home/sumeet/Downloads/arpack-ng/PARPACK'</div>
</div>
<div>
<div>make: *** [install-recursive]
Error 1</div>
</div>
<div><br>
</div>
</blockquote>
Any ideas about resolving this error?</div>
</blockquote>
</div>
</div>
Two things:<br>
* install a fortran compiler and restart the
configure<br>
* please report a bug about on the arpack-ng
forge. We should stop the configure if the
fortran compiler is not found.<br>
<br>
Thanks,<br>
Sylvestre<span><font color="#888888"><br>
<br>
<br>
<pre cols="72">--
-----------------------------
Sylvestre Ledru
Operation manager
Community manager
-----------------------------
Scilab Enterprises
<a href="http://www.scilab-enterprises.com/" target="_blank">http://www.scilab-enterprises.com/</a>
<a href="http://www.scilab.org/" target="_blank">http://www.scilab.org/</a>
-----------------------------
</pre>
</font></span></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
<br>
<pre cols="72">--
-----------------------------
Sylvestre Ledru
Operation manager
Community manager
-----------------------------
Scilab Enterprises
<a href="http://www.scilab-enterprises.com/" target="_blank">http://www.scilab-enterprises.com/</a>
<a href="http://www.scilab.org/" target="_blank">http://www.scilab.org/</a>
-----------------------------
</pre>
</div></div></div>
</blockquote></div><br></div>