mac installation error.

76 views
Skip to first unread message

Anthony Colombo

unread,
Feb 8, 2015, 11:15:50 PM2/8/15
to libflame...@googlegroups.com
Hello. I am having issues installing the software on my mac.


here is the error. looking for troubleshooting tips


Anthonys-MBP:libflame anthonycolombo60$ ./configure --enable-supermatrix --enable-multithreading=pthreads --disable-internal-error-checking
cat: version: No such file or directory
checking build system type... x86_64-apple-darwin14.1.0
checking host system type... x86_64-apple-darwin14.1.0
checking for GNU make... make
checking for GNU bash... bash
checking whether user requested a specific C compiler... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C 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 C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether user requested a specific library archiver... no
checking for ar... ar
checking whether user requested a specific library archive indexer... no
checking for ranlib... ranlib
checking for a BSD-compatible install... /usr/bin/install -c
checking for find... find
checking for xargs... xargs
checking whether ln -s works... yes
checking whether user requested auto-detection of Fortran linker flags... yes
checking whether user requested auto-detection of Fortran name-mangling... 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 pgfortran... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking how to get verbose linking output from ... configure: WARNING: compilation failed

checking for Fortran 77 libraries of ...
checking for dummy main to link with Fortran 77 libraries... none
checking for Fortran 77 name-mangling scheme... configure: error: in `/Users/anthonycolombo60/Documents/Online Learning/Linear Algebra LAFF/libflame':
configure: error: cannot compile a simple Fortran program
See `config.log' for more details

Field Van Zee

unread,
Feb 9, 2015, 12:22:48 PM2/9/15
to libflame...@googlegroups.com
Anthony,

I don't use OS X, but based on the error message I will just take a stab in the dark and say that you need to disable the auto-detection of Fortran. Try adding the following configure options:

--disable-autodetect-f77-ldflags
--disable-autodetect-f77-name-mangling

A full list of configure options can be seen via './configure --help'.

Field

Anthony Colombo

unread,
Feb 10, 2015, 7:36:49 PM2/10/15
to libflame...@googlegroups.com
Hi, So I reinstalled lapack and blas and made some progress.

here is my message, it is something to do with Xcode, but I am not sure if this is a serious warning or not.


Compiling src/lapack/util/app/qut/rhfr/flamec/FLA_Apply_Q_UT_rhfr_blk_var1.c
Compiling src/lapack/util/app/qut/rhfr/flamec/FLA_Apply_Q_UT_rhfr_blk_var2.c
Compiling src/lapack/util/app/qut/rhfr/flamec/FLA_Apply_Q_UT_rhfr_blk_var3.c
Compiling src/lapack/util/app/qut/rnbc/flamec/FLA_Apply_Q_UT_rnbc_blk_var1.c
Compiling src/lapack/util/app/qut/rnbc/flamec/FLA_Apply_Q_UT_rnbc_blk_var2.c
Compiling src/lapack/util/app/qut/rnbc/flamec/FLA_Apply_Q_UT_rnbc_blk_var3.c
Compiling src/lapack/util/app/qut/rnbr/flamec/FLA_Apply_Q_UT_rnbr_blk_var1.c
Compiling src/lapack/util/app/qut/rnbr/flamec/FLA_Apply_Q_UT_rnbr_blk_var2.c
Compiling src/lapack/util/app/qut/rnbr/flamec/FLA_Apply_Q_UT_rnbr_blk_var3.c
Compiling src/lapack/util/app/qut/rnfc/flamec/FLA_Apply_Q_UT_rnfc_blk_var1.c
Compiling src/lapack/util/app/qut/rnfc/flamec/FLA_Apply_Q_UT_rnfc_blk_var2.c
Compiling src/lapack/util/app/qut/rnfc/flamec/FLA_Apply_Q_UT_rnfc_blk_var3.c
Compiling src/lapack/util/app/qut/rnfr/flamec/FLA_Apply_Q_UT_rnfr_blk_var1.c
Compiling src/lapack/util/app/qut/rnfr/flamec/FLA_Apply_Q_UT_rnfr_blk_var2.c
Compiling src/lapack/util/app/qut/rnfr/flamec/FLA_Apply_Q_UT_rnfr_blk_var3.c
Compiling src/lapack/util/app/qutinc/front/flamec/FLASH_Apply_Q_UT_inc.c
Compiling src/lapack/util/app/qutinc/front/flamec/FLASH_Apply_Q_UT_inc_create_workspace.c
Compiling src/lapack/util/app/qutinc/front/flamec/FLA_Apply_Q_UT_inc_internal.c
Compiling src/lapack/util/app/qutinc/front/flamec/FLA_Apply_Q_UT_inc_lhfc.c
Compiling src/lapack/util/app/qutinc/front/flamec/FLA_Apply_Q_UT_inc_lnfc.c
Compiling src/lapack/util/app/qutinc/lhfc/flamec/FLA_Apply_Q_UT_inc_lhfc_blk_var1.c
Compiling src/lapack/util/app/qutinc/lnfc/flamec/FLA_Apply_Q_UT_inc_lnfc_blk_var1.c
Archiving lib/x86_64-apple-darwin14.1.0/libflame.a
darwin14.1.0/libflame.a(FLASH_Queue_exec.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Axpy_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Copy_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolcdarwin14.1.0/libflame.a(FLA_Trsv_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Gemm_external_gpu.o) has no symbols
darwin14.1.0/libflame.a(FLA_Scalr_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Gemv_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Trsv_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Gemm_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Hemm_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Her2k_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Herk_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Symm_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Syr2k_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Syrk_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Trmm_external_gpu.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: lib/x86_64-apple-darwin14.1.0/libflame.a(FLA_Trsm_external_gpu.o) has no symbols
Anthonys-MBP:libflame anthonycolombo60$ ls
AUTHORS Makefile config.status include_local tmp
CHANG


======================


Anthonys-MBP:libflame anthonycolombo60$ make check
make: Nothing to be done for `check'.
Anthonys-MBP:libflame anthonycolombo60$ ls
AUTHORS Makefile config.status include_local tmp
CHANGELOG Makefile_tidsp config.sys_type lapack-test version
CONTRIBUTORS README configure lib windows
Doxyfile bootstrap configure.ac obj
INSTALL build configure_tidsp run-conf
KNOWN-ISSUES config docs src
LICENSE config.log examples test
Anthonys-MBP:libflame anthonycolombo60$ make check
make: Nothing to be done for `check'.
Anthonys-MBP:libflame anthonycolombo60$ make install
Installing libflame-x86_64-5.1.0-18.a into /Users/anthonycolombo60/flame/lib/
Installing C header files into /Users/anthonycolombo60/flame/include-x86_64-5.1.0-18
Installing symlink libflame.a into /Users/anthonycolombo60/flame/lib/
Installing symlink include into /Users/anthonycolombo60/flame/

Anthony Colombo

unread,
Feb 10, 2015, 7:37:30 PM2/10/15
to libflame...@googlegroups.com
On Monday, February 9, 2015 at 9:22:48 AM UTC-8, Field Van Zee wrote:

Can you confirm that this is the correct library? it only shows one library on my end.. should there be multiples?

Field G. Van Zee

unread,
Feb 10, 2015, 8:03:34 PM2/10/15
to libflame...@googlegroups.com
Anthony,

You should be able to safely ignore the "has no symbols" messages.

Field

Anthony Colombo

unread,
Feb 10, 2015, 8:05:02 PM2/10/15
to libflame...@googlegroups.com

Are these the correct file sizes?

Anthonys-MBP:Downloads anthonycolombo60$ ls /Users/anthonycolombo60/flame/
include include-x86_64-5.1.0-18 lib
Anthonys-MBP:Downloads anthonycolombo60$ du -h /Users/anthonycolombo60/flame/
2.1M /Users/anthonycolombo60/flame//include-x86_64-5.1.0-18
12M /Users/anthonycolombo60/flame//lib
14M /Users/anthonycolombo60/flame/

Field G. Van Zee

unread,
Feb 10, 2015, 8:05:33 PM2/10/15
to libflame...@googlegroups.com
Anthony,

Could you please clarify your question?

There is only one libflame library file: a '.a' static archive. (You can also
get an '.so' file if shared output is enabled.)

Field

Anthony Colombo

unread,
Feb 10, 2015, 8:09:40 PM2/10/15
to Field G. Van Zee, libflame...@googlegroups.com
Thank you very much for your response.

I just wanted to confirm with an experienced user if my directories were the correct size because this might imply the correct content.  I am still working on testing the install.

my static .a library directory is 12M 
but also wanted to check the headers under the include directory as well which is 2M in size.

Thank you again.


Anthony Colombo
University of Southern California
Applied Mathematics (B.S.)  and Physics (Minor)
Fall '14

--
You received this message because you are subscribed to a topic in the Google Groups "libflame-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/libflame-discuss/AMhkPMdZKTk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to libflame-discu...@googlegroups.com.
To post to this group, send email to libflame...@googlegroups.com.
Visit this group at http://groups.google.com/group/libflame-discuss.
For more options, visit https://groups.google.com/d/optout.

Field G. Van Zee

unread,
Feb 10, 2015, 8:29:31 PM2/10/15
to libflame...@googlegroups.com
Anthony,

The file sizes are about right. libflame is quite large.

Glad I could help.

Field

On 02/10/15 19:09, Anthony Colombo wrote:
> Thank you very much for your response.
>
> I just wanted to confirm with an experienced user if my directories were the
> correct size because this might imply the correct content. I am still working
> on testing the install.
>
> my static .a library directory is 12M
> but also wanted to check the headers under the include directory as well which
> is 2M in size.
>
> Thank you again.
>
>
> Anthony Colombo
> University of Southern California
> Applied Mathematics (B.S.) and Physics (Minor)
> Fall '14
>
>> On Feb 10, 2015, at 5:05 PM, Field G. Van Zee <fi...@cs.utexas.edu
>> <mailto:fi...@cs.utexas.edu>> wrote:
>>
>> Anthony,
>>
>> Could you please clarify your question?
>>
>> There is only one libflame library file: a '.a' static archive. (You can
>> also get an '.so' file if shared output is enabled.)
>>
>> Field
>>
>> On 02/10/15 18:37, Anthony Colombo wrote:
>>
>>>
>>> Can you confirm that this is the correct library? it only shows one
>>> library on my end.. should there be multiples?
>>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "libflame-discuss" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/libflame-discuss/AMhkPMdZKTk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> libflame-discu...@googlegroups.com
>> <mailto:libflame-discu...@googlegroups.com>.
>> To post to this group, send email to libflame...@googlegroups.com
>> <mailto:libflame...@googlegroups.com>.
>> Visit this group at http://groups.google.com/group/libflame-discuss.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "libflame-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to libflame-discu...@googlegroups.com
> <mailto:libflame-discu...@googlegroups.com>.
> To post to this group, send email to libflame...@googlegroups.com
> <mailto:libflame...@googlegroups.com>.
Reply all
Reply to author
Forward
0 new messages