[scilab-Users] arpack-ng compile error

Sumeet sumeetsk at gmail.com
Thu Mar 29 19:45:18 CEST 2012 

For the archives: This issue has been reported and resolved on
http://forge.scilab.org/index.php/p/arpack-ng/issues/689/ My bad, I didn't
check earlier.

On Thu, Mar 29, 2012 at 10:58 PM, Sumeet <sumeetsk at gmail.com> wrote:

> I'm sorry, I will.
>
>
> On Thu, Mar 29, 2012 at 10:52 PM, Sylvestre Ledru <
> sylvestre.ledru at scilab-enterprises.com> wrote:
>
>> **
>> 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.
>>
>>
>> On 29/03/2012 19:18, Sumeet wrote:
>>
>> Thanks Sylvestre and Charlie.
>>
>>  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.
>>
>>  Thanks,
>> Sumeet.
>>
>>  In case this helps, here's the ./configure output on removing
>> fortran77-compiler:
>>
>>  checking for a BSD-compatible install... /usr/bin/install -c
>>  checking whether build environment is sane... yes
>>  checking for a thread-safe mkdir -p... /bin/mkdir -p
>>  checking for gawk... gawk
>>  checking whether make sets $(MAKE)... yes
>>  checking for g77... no
>>  checking for xlf... no
>>  checking for f77... no
>>  checking for frt... no
>>  checking for pgf77... no
>>  checking for cf77... no
>>  checking for fort77... no
>>  checking for fl32... no
>>  checking for af77... no
>>  checking for xlf90... no
>>  checking for f90... no
>>  checking for pgf90... no
>>  checking for pghpf... no
>>  checking for epcf90... no
>>  checking for gfortran... no
>>  checking for g95... no
>>  checking for xlf95... no
>>  checking for f95... no
>>  checking for fort... no
>>  checking for ifort... no
>>  checking for ifc... no
>>  checking for efc... no
>>  checking for pgf95... no
>>  checking for lf95... no
>>  checking for ftn... no
>>  checking whether the Fortran 77 compiler works... no
>>  configure: error: in `/home/sumeet/Downloads/arpack-ng':
>>  configure: error: Fortran 77 compiler cannot create executables
>>  See `config.log' for more details.
>>
>>
>>  Here's the ./configure output with fortran77-compiler present:
>>
>>  checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>> checking for gawk... gawk
>> checking whether make sets $(MAKE)... yes
>> checking for g77... no
>> checking for xlf... no
>> checking for f77... f77
>> checking whether the Fortran 77 compiler works... yes
>> checking for Fortran 77 compiler default output file name... a.out
>> checking for suffix of executables...
>> checking whether we are cross compiling... no
>> checking for suffix of object files... o
>> checking whether we are using the GNU Fortran 77 compiler... yes
>> checking whether f77 accepts -g... yes
>> checking build system type... i686-pc-linux-gnu
>> checking host system type... i686-pc-linux-gnu
>> checking how to print strings... printf
>> checking for style of include used by make... GNU
>> checking for gcc... gcc
>> 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 dependency style of gcc... none
>> checking for a sed that does not truncate output... /bin/sed
>> checking for grep that handles long lines and -e... /bin/grep
>> checking for egrep... /bin/grep -E
>> checking for fgrep... /bin/grep -F
>> checking for ld used by gcc... /usr/bin/ld
>> checking if the linker (/usr/bin/ld) is GNU ld... yes
>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
>> checking the name lister (/usr/bin/nm -B) interface... BSD nm
>> checking whether ln -s works... yes
>> checking the maximum length of command line arguments... 1572864
>> checking whether the shell understands some XSI constructs... yes
>> checking whether the shell understands "+="... yes
>> checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu
>> format... func_convert_file_noop
>> checking how to convert i686-pc-linux-gnu file names to toolchain
>> format... func_convert_file_noop
>> checking for /usr/bin/ld option to reload object files... -r
>> checking for objdump... objdump
>> checking how to recognize dependent libraries... pass_all
>> checking for dlltool... no
>>  checking how to associate runtime and link libraries... printf %s\n
>> checking for ar... ar
>> checking for archiver @FILE support... @
>> checking for strip... strip
>> checking for ranlib... ranlib
>> checking command to parse /usr/bin/nm -B output from gcc object... ok
>> checking for sysroot... no
>> checking for mt... mt
>> checking if mt is a manifest tool... no
>> checking how to run the C preprocessor... gcc -E
>> 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... -fPIC -DPIC
>> checking if gcc PIC flag -fPIC -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/bin/ld) supports shared
>> libraries... yes
>> checking whether -lc should be explicitly linked in... no
>> checking dynamic linker characteristics... GNU/Linux ld.so
>> 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 if libtool supports shared libraries... yes
>> checking whether to build shared libraries... yes
>> checking whether to build static libraries... yes
>> checking for f77 option to produce PIC... -fPIC
>> checking if f77 PIC flag -fPIC works... yes
>> checking if f77 static flag -static works... yes
>> checking if f77 supports -c -o file.o... yes
>> checking if f77 supports -c -o file.o... (cached) yes
>> checking whether the f77 linker (/usr/bin/ld) supports shared
>> libraries... yes
>> checking dynamic linker characteristics... (cached) GNU/Linux ld.so
>> checking how to hardcode library paths into programs... immediate
>> checking how to get verbose linking output from f77... configure:
>> WARNING: cannot determine how to obtain linking information from f77
>>
>>  checking for Fortran 77 libraries of f77...
>> checking for dummy main to link with Fortran 77 libraries... none
>> checking for Fortran 77 name-mangling scheme... lower case, underscore,
>> extra underscore
>> checking if sgemm_ is being linked in already... no
>> checking for ATL_xerbla in -latlas... no
>> checking for sgemm_ in -lblas... yes
>> checking for dgemm_ in -ldgemm... no
>> checking for sgemm_ in -lmkl... no
>> checking for sgemm_ in -framework vecLib... no
>> checking for sgemm_ in -lcxml... no
>> checking for sgemm_ in -ldxml... no
>> checking for sgemm_ in -lscs... no
>> checking for sgemm_ in -lcomplib.sgimath... no
>> checking for sgemm_ in -lblas... (cached) yes
>> checking for sgemm_ in -lessl... no
>> checking for sgemm_ in -lblas... (cached) yes
>> checking for cheev_... no
>> checking for cheev_ in -llapack... yes
>> checking for MPI mode... configure: creating ./config.status
>> config.status: creating Makefile
>> config.status: creating SRC/Makefile
>> config.status: creating UTIL/Makefile
>> config.status: creating TESTS/Makefile
>> config.status: creating PARPACK/Makefile
>> config.status: creating PARPACK/SRC/Makefile
>> config.status: creating PARPACK/SRC/MPI/Makefile
>> config.status: creating PARPACK/UTIL/Makefile
>> config.status: creating PARPACK/UTIL/MPI/Makefile
>> config.status: executing depfiles commands
>> config.status: executing libtool commands
>>
>>
>> On Thu, Mar 29, 2012 at 10:20 PM, Charles Warner <cwarner.cw711 at gmail.com
>> > wrote:
>>
>>> 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.
>>> 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.
>>>
>>>  Charlie
>>>
>>>
>>> On Thu, Mar 29, 2012 at 11:27 AM, Sylvestre Ledru <
>>> sylvestre.ledru at scilab-enterprises.com> wrote:
>>>
>>>>   On 29/03/2012 18:23, Sumeet wrote:
>>>>
>>>> Hi,
>>>>
>>>>  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.
>>>>
>>>>  I get the following error:
>>>>
>>>>   Making install in PARPACK
>>>>  make[1]: Entering directory `/home/sumeet/Downloads/arpack-ng/PARPACK'
>>>>  Making install in UTIL
>>>>  make[2]: Entering directory
>>>> `/home/sumeet/Downloads/arpack-ng/PARPACK/UTIL'
>>>>  Making install in MPI
>>>>  make[3]: Entering directory
>>>> `/home/sumeet/Downloads/arpack-ng/PARPACK/UTIL/MPI'
>>>>  /bin/bash ../../../libtool --tag=F77   --mode=compile   -g -O2 -c -o
>>>> pivout.lo pivout.f
>>>>  libtool: compile: unrecognized option `-g'
>>>>  libtool: compile: Try `libtool --help' for more information.
>>>>  make[3]: *** [pivout.lo] Error 1
>>>>  make[3]: Leaving directory
>>>> `/home/sumeet/Downloads/arpack-ng/PARPACK/UTIL/MPI'
>>>>  make[2]: *** [install-recursive] Error 1
>>>>  make[2]: Leaving directory
>>>> `/home/sumeet/Downloads/arpack-ng/PARPACK/UTIL'
>>>>  make[1]: *** [install-recursive] Error 1
>>>>  make[1]: Leaving directory `/home/sumeet/Downloads/arpack-ng/PARPACK'
>>>>  make: *** [install-recursive] Error 1
>>>>
>>>>  Any ideas about resolving this error?
>>>>
>>>>  Two things:
>>>> * install a fortran compiler and restart the configure
>>>> * please report a bug about on the arpack-ng forge. We should stop the
>>>> configure if the fortran compiler is not found.
>>>>
>>>> Thanks,
>>>> Sylvestre
>>>>
>>>>
>>>> --
>>>> -----------------------------
>>>> Sylvestre Ledru
>>>> Operation manager
>>>> Community manager
>>>> -----------------------------
>>>> Scilab Enterpriseshttp://www.scilab-enterprises.com/http://www.scilab.org/
>>>> -----------------------------
>>>>
>>>>
>>>
>>
>>
>> --
>> -----------------------------
>> Sylvestre Ledru
>> Operation manager
>> Community manager
>> -----------------------------
>> Scilab Enterpriseshttp://www.scilab-enterprises.com/http://www.scilab.org/
>> -----------------------------
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/users/attachments/20120329/cb256f2a/attachment.htm>

More information about the users mailing list