Date: Fri, 28 Jul 2006 16:26:44 GMT From: Masayuki Takemura <ICG04984@nifty.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/100991: math/atlas-3.6.0, 1 compilation fails when WITH_OPTIMIZED_OPTION is specified Message-ID: <200607281626.k6SGQiNi087227@www.freebsd.org> Resent-Message-ID: <200607281630.k6SGUFt5083757@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 100991 >Category: ports >Synopsis: math/atlas-3.6.0,1 compilation fails when WITH_OPTIMIZED_OPTION is specified >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jul 28 16:30:14 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Masayuki Takemura >Release: 6.1-RELEASE i386 >Organization: >Environment: FreeBSD suger.localhost 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7 04:32:43 UTC 2006 root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 PC: Toshiba Dynabook SS 3490 CPU: Pentium III 700MHz Memory: 128MB URL: <http://dynabook.com/pc/catalog/ss/010228ds/spec.htm>; >Description: Atlas exits with the following error, when I compiled it with WITH_OPTIMIZED_OPTION. ===> Building for lapack-3.0_1 ( cd INSTALL; make; ./testlsame; ./testslamch; ./testdlamch; ./testsecond; ./testdsecnd; cp lsame.f ../BLAS/SRC/; cp lsame.f ../SRC; cp slamch.f ../SRC/; cp dlamch.f ../SRC/; cp second.f ../SRC/; cp dsecnd.f ../SRC/; cp etime_.c ../SRC/ ) f77 -O -mtune= -pipe -O2 -ffast-math -fomit-frame-pointer -c lsame.f lsame.f:0: error: bad value () for -mtune= switch *** Error code 1 Stop in /usr/ports/math/atlas/work/lapack/work/LAPACK/INSTALL. *** Error code 1 Stop in /usr/ports/math/atlas/work/lapack/work/LAPACK. *** Error code 1 Stop in /usr/ports/math/atlas/work/lapack. *** Error code 1 Stop in /usr/ports/math/atlas. -- error log ends here -- An entire compilation log is below: ===> Extracting for atlas-3.6.0,1 => MD5 Checksum OK for atlas3.6.0.tar.bz2. => SHA256 Checksum OK for atlas3.6.0.tar.bz2. ===> Patching for atlas-3.6.0,1 ===> Applying FreeBSD patches for atlas-3.6.0,1 ===> Configuring for atlas-3.6.0,1 Warning: Building this port can take long time for slow computers (over 1 day). And sometimes stop building for Athlon. In this case please retype make or rebuild whole atlas. Warning: If your arch is not correctly detected, you can specify by yourself. for example : make PORTS_ARCH=P5Int Available architectures for x86 are: IntP5, IntP5MMX, IntPPRO, IntPII, IntPIII, IntP4, IntP4E IntP4E64, TMEff, AmdAthlon,AmdHammer32, AmdHammer64 If your install dies with unable to get timings in tolerance First please refer http://math-atlas.sourceforge.net/errata.html#tol and you can build with make clean; make -DTIMING_TOLERANCE if your build still dies, you can type make again, (and again...) You can build static libraries with make -DWITH_STATICLIB gcc -o xconfig config.c /var/tmp//ccHaYhDg.o(.text+0x871): In function `CmndResults': : warning: warning: tmpnam() possibly used unsafely; consider using mkstemp() make: illegal option -- - usage: make [-BPSXeiknqrstv] [-C directory] [-D variable] [-d flags] [-E variable] [-f makefile] [-I directory] [-j max_jobs] [-m directory] [-V variable] [variable=value] [target ...] ATLAS3.6.0 configure started. 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 099 098 097 096 095 094 093 092 091 090 089 088 087 086 085 084 083 082 081 080 079 078 077 076 075 074 073 072 071 070 069 068 067 066 065 064 063 062 061 060 059 058 057 056 055 054 053 052 051 050 049 048 047 046 045 044 043 042 041 040 039 038 037 036 035 034 033 032 031 030 029 028 027 026 025 024 023 022 021 020 019 018 017 016 015 014 013 012 011 010 009 008 007 006 005 004 003 002 001 Enter number at top left of screen [0]: =============================================================================== IMPORTANT =============================================================================== Before going any further, check http://math-atlas.sourceforge.net/errata.html This is the ATLAS errata file, which keeps a running count of all known ATLAS bugs and system problems, with associated workarounds or fixes. IF YOU DO NOT CHECK THIS FILE, YOU MAY BE COMPILING A LIBRARY WITH KNOWN BUGS. Have you scoped the errata file? [y]: Configure will ask a series of questions, in one of two forms. The first form of question is a menu of choices. One option in almost all menus is 'Other/UNKNOWN'. If you are unsure of the answer, always choose this option. The second form of question is a single line, with a default answer shown in square braces. If you hit return without typing anything, this default answer will be used. Again, if you are unsure of the answer, simply accept the default. ATLAS can detect almost everything it needs to know, so choosing the default or 'Other/UNKNOWN' will at worst simply extend the install time (if you tell config the answer to something ATLAS can skip some tests). Configure makes no changes to the state of things until all questions have been asked and answered. Therefore, if you get confused and want to start over, feel free to break out of this program (CTRL-C, CTRL-BREAK, etc) and start again. Alternatively, if you make a mistake you can finish the configure process, and then edit the created make include file by hand to fix the mistake manually (the name and location of this file will be printed out at the end of configure). If you have problems during configure or installation, consult the file 'ATLAS/README/TroubleShoot.txt'. Are you ready to continue? [y]: Probing to make operating system determination: Operating system configured as FreeBSD Probing for architecture: Architecture is set to PIII Probing for supported ISA extensions: AltiVec: NO. AltiVec: NO. SSE2: NO. SSE1: DETECTED! Number of CPUs: 1 Looking for compilers (this may take a while): cc : v3.4.4 F77 = /usr/bin/f77 -O CC = /usr/bin/cc -fomit-frame-pointer -O3 -funroll-all-loops MCC = /usr/bin/cc -fomit-frame-pointer -O FINDING tar, gzip, AND gunzip tar : /usr/bin/tar gzip : /usr/bin/gzip gunzip : /usr/bin/gunzip ATLAS has default parameters for OS='FreeBSD' and system='PIII'. If you want to just trust these default values, you can use express setup, drastically reducing the amount of questions you are required to answer use express setup? [y]: You need to choose a name which represents this architecture (eg. UltraSparc, Dec21164, etc). Do not use a generic name (eg. solaris, linux), which might apply to different hardware. This architecture name will be appended to the name of the created make include file, and appear in all subdirectories, so don't make it longer than you like to type. The name should follow the rules for file names (so don't use punctuation and spaces, for instance). <arch> set to 'NON_THREADED' This next value is the size, in kilobytes, that ATLAS must read/write in order to completely flush your largest cache. ATLAS will flush this much memory between timing calls, in order to ensure timings are not inflated by cache preloading. A safe maximum is usually twice the size of your actual largest cache size. If you do not know the size of your largest cache, a maximum value is fine. The only drawback to making this value large is that it requires more memory to do timings, and may slow down the install process (if you have only a small amount of memory, it can also invalidate the timings by causing the timers to swap). The default given below is ATLAS's idea of either the maximum cache your system could have, or the maximum ATLAS believes it is safe to flush. If you are certain that your largest cache is smaller than the default given below, expedite the install by changing it. If you are certain you have enough memory to support the necessary memory demands without swapping, and the value is not twice the size of your largest cache, increase it. Otherwise, just hit enter to continue. Enter Maximum cache size (KB) [512]: The ATLAS install process is heavily file-based, and this can cause major reliability problems when interacting with an overloaded or malfunctioning remotely mounted filesystem. ATLAS therefore has a mechanism in place to allow for a delay before a file is declared to not be there, so that slow NFS (i.e., waiting for amd timout) problems can be overcome, or for handling slightly differing clocks between server/client. This problem is magnified if doing cross-compilation. In the question below, we ask how much of a delay, in seconds, ATLAS should tolerate between file creation and appearance. If you are installing on a local filesystem (eg. /tmp) or a smooth-running NFS system, answer 0; for a moderately loaded NFS server, you may want a value in the 10 second range, and for cross-compiling systems or NFS servers experiencing errors, you may want to go as high as a couple of minutes (120). Enter File creation delay in seconds [0]: I'm going to ask you for information about your Fortran 77 compiler. ATLAS does not need Fortran77 to build, so if you don't have a Fortran compiler, the install can still be completed successfully. However, ATLAS built without a Fortran compiler will not be callable from Fortran (i.e., the user should use the C interface), and we will not be able to do full testing, since some of the tester code is written in Fortran77. F77 & FLAGS: /usr/bin/f77 -O FLINKER & FLAGS: $(F77) $(F77FLAGS) CC & FLAGS: /usr/bin/cc -fomit-frame-pointer -O3 -funroll-all-loops MCC & FLAGS: /usr/bin/cc -fomit-frame-pointer -O CLINKER & FLAGS: $(CC) $(CCFLAGS) Finding F77 to C calling conventions (this may take a while): Calculated F77/C interoperation conventions: Suffix F77 names with underscores with __ F77 INTEGER -> C int F77 strings handled via standard sun style The ATLAS team has provided a default install for your architecture. If you want, these default values can be used, and ATLAS can skip most of the search for your machine. This will greatly decrease the amount of time required for the install, allow you to take advantage of any special features found by the ATLAS team, and provide protection against install miscues caused by unreliable timing results, assuming you really have the machine ATLAS thinks you have. If your machine is non-standard in some way, or you just want to see the ATLAS search for yourself, you should answer no to the following question. Otherwise, it is highly recommended to accept the default of yes. Use supplied default values for install? [y]: Unpacking Architectural defaults . . . done. Your architectural defaults do not include defaults for the Level 1 BLAS. ATLAS now has the ability to tune the Level 1 BLAS to your machine. However, this will add time to the install. If your algorithm utilizes the Level 2 or Level 3 BLAS to any degree, the the Level 1 BLAS will usually be a low order term, and thus only matter for small problems. Therefore, if you don't think you need good performance from the Level 1 BLAS, you can answer "no" to the question below, and ATLAS will skip the Level 1 tuning. ATLAS will still provide Level 1 BLAS, but their performance may be much worse than if tuning were allowed. Tune the Level 1 BLAS? [y]: Creating make include file Make.NON_THREADED Make.NON_THREADED successfully created. Creating ATLrun.sh Creating subdirectories: Checking for already existing subdirectories ........ no Subdirectories successfully created. Moving config logfiles ConfSummary.log and ConfDump.log to bin/NON_THREADED/INSTALL_LOG/ Configuration completed successfully. You may want to examine the make include file (Make.NON_THREADED) for accuracy before starting the install with the command: make install arch=NON_THREADED make: illegal option -- - usage: make [-BPSXeiknqrstv] [-C directory] [-D variable] [-d flags] [-E variable] [-f makefile] [-I directory] [-j max_jobs] [-m directory] [-V variable] [variable=value] [target ...] ATLAS3.6.0 configure started. 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 099 098 097 096 095 094 093 092 091 090 089 088 087 086 085 084 083 082 081 080 079 078 077 076 075 074 073 072 071 070 069 068 067 066 065 064 063 062 061 060 059 058 057 056 055 054 053 052 051 050 049 048 047 046 045 044 043 042 041 040 039 038 037 036 035 034 033 032 031 030 029 028 027 026 025 024 023 022 021 020 019 018 017 016 015 014 013 012 011 010 009 008 007 006 005 004 003 002 001 Enter number at top left of screen [0]: =============================================================================== IMPORTANT =============================================================================== Before going any further, check http://math-atlas.sourceforge.net/errata.html This is the ATLAS errata file, which keeps a running count of all known ATLAS bugs and system problems, with associated workarounds or fixes. IF YOU DO NOT CHECK THIS FILE, YOU MAY BE COMPILING A LIBRARY WITH KNOWN BUGS. Have you scoped the errata file? [y]: Configure will ask a series of questions, in one of two forms. The first form of question is a menu of choices. One option in almost all menus is 'Other/UNKNOWN'. If you are unsure of the answer, always choose this option. The second form of question is a single line, with a default answer shown in square braces. If you hit return without typing anything, this default answer will be used. Again, if you are unsure of the answer, simply accept the default. ATLAS can detect almost everything it needs to know, so choosing the default or 'Other/UNKNOWN' will at worst simply extend the install time (if you tell config the answer to something ATLAS can skip some tests). Configure makes no changes to the state of things until all questions have been asked and answered. Therefore, if you get confused and want to start over, feel free to break out of this program (CTRL-C, CTRL-BREAK, etc) and start again. Alternatively, if you make a mistake you can finish the configure process, and then edit the created make include file by hand to fix the mistake manually (the name and location of this file will be printed out at the end of configure). If you have problems during configure or installation, consult the file 'ATLAS/README/TroubleShoot.txt'. Are you ready to continue? [y]: Probing to make operating system determination: Operating system configured as FreeBSD Probing for architecture: Architecture is set to PIII Probing for supported ISA extensions: AltiVec: NO. AltiVec: NO. SSE2: NO. SSE1: DETECTED! Number of CPUs: 1 Looking for compilers (this may take a while): cc : v3.4.4 F77 = /usr/bin/f77 -fpic -DPIC -O CC = /usr/bin/cc -fomit-frame-pointer -O3 -funroll-all-loops MCC = /usr/bin/cc -fomit-frame-pointer -O FINDING tar, gzip, AND gunzip tar : /usr/bin/tar gzip : /usr/bin/gzip gunzip : /usr/bin/gunzip ATLAS has default parameters for OS='FreeBSD' and system='PIII'. If you want to just trust these default values, you can use express setup, drastically reducing the amount of questions you are required to answer use express setup? [y]: You need to choose a name which represents this architecture (eg. UltraSparc, Dec21164, etc). Do not use a generic name (eg. solaris, linux), which might apply to different hardware. This architecture name will be appended to the name of the created make include file, and appear in all subdirectories, so don't make it longer than you like to type. The name should follow the rules for file names (so don't use punctuation and spaces, for instance). <arch> set to 'NON_THREADED_PIC' This next value is the size, in kilobytes, that ATLAS must read/write in order to completely flush your largest cache. ATLAS will flush this much memory between timing calls, in order to ensure timings are not inflated by cache preloading. A safe maximum is usually twice the size of your actual largest cache size. If you do not know the size of your largest cache, a maximum value is fine. The only drawback to making this value large is that it requires more memory to do timings, and may slow down the install process (if you have only a small amount of memory, it can also invalidate the timings by causing the timers to swap). The default given below is ATLAS's idea of either the maximum cache your system could have, or the maximum ATLAS believes it is safe to flush. If you are certain that your largest cache is smaller than the default given below, expedite the install by changing it. If you are certain you have enough memory to support the necessary memory demands without swapping, and the value is not twice the size of your largest cache, increase it. Otherwise, just hit enter to continue. Enter Maximum cache size (KB) [512]: The ATLAS install process is heavily file-based, and this can cause major reliability problems when interacting with an overloaded or malfunctioning remotely mounted filesystem. ATLAS therefore has a mechanism in place to allow for a delay before a file is declared to not be there, so that slow NFS (i.e., waiting for amd timout) problems can be overcome, or for handling slightly differing clocks between server/client. This problem is magnified if doing cross-compilation. In the question below, we ask how much of a delay, in seconds, ATLAS should tolerate between file creation and appearance. If you are installing on a local filesystem (eg. /tmp) or a smooth-running NFS system, answer 0; for a moderately loaded NFS server, you may want a value in the 10 second range, and for cross-compiling systems or NFS servers experiencing errors, you may want to go as high as a couple of minutes (120). Enter File creation delay in seconds [0]: I'm going to ask you for information about your Fortran 77 compiler. ATLAS does not need Fortran77 to build, so if you don't have a Fortran compiler, the install can still be completed successfully. However, ATLAS built without a Fortran compiler will not be callable from Fortran (i.e., the user should use the C interface), and we will not be able to do full testing, since some of the tester code is written in Fortran77. F77 & FLAGS: /usr/bin/f77 -fpic -DPIC -O FLINKER & FLAGS: $(F77) $(F77FLAGS) CC & FLAGS: /usr/bin/cc -fomit-frame-pointer -O3 -funroll-all-loops MCC & FLAGS: /usr/bin/cc -fomit-frame-pointer -O CLINKER & FLAGS: $(CC) $(CCFLAGS) Finding F77 to C calling conventions (this may take a while): Calculated F77/C interoperation conventions: Suffix F77 names with underscores with __ F77 INTEGER -> C int F77 strings handled via standard sun style The ATLAS team has provided a default install for your architecture. If you want, these default values can be used, and ATLAS can skip most of the search for your machine. This will greatly decrease the amount of time required for the install, allow you to take advantage of any special features found by the ATLAS team, and provide protection against install miscues caused by unreliable timing results, assuming you really have the machine ATLAS thinks you have. If your machine is non-standard in some way, or you just want to see the ATLAS search for yourself, you should answer no to the following question. Otherwise, it is highly recommended to accept the default of yes. Use supplied default values for install? [y]: Unpacking Architectural defaults . . . done. Your architectural defaults do not include defaults for the Level 1 BLAS. ATLAS now has the ability to tune the Level 1 BLAS to your machine. However, this will add time to the install. If your algorithm utilizes the Level 2 or Level 3 BLAS to any degree, the the Level 1 BLAS will usually be a low order term, and thus only matter for small problems. Therefore, if you don't think you need good performance from the Level 1 BLAS, you can answer "no" to the question below, and ATLAS will skip the Level 1 tuning. ATLAS will still provide Level 1 BLAS, but their performance may be much worse than if tuning were allowed. Tune the Level 1 BLAS? [y]: Creating make include file Make.NON_THREADED_PIC Make.NON_THREADED_PIC successfully created. Creating ATLrun.sh Creating subdirectories: Checking for already existing subdirectories ........ no Subdirectories successfully created. Moving config logfiles ConfSummary.log and ConfDump.log to bin/NON_THREADED_PIC/INSTALL_LOG/ Configuration completed successfully. You may want to examine the make include file (Make.NON_THREADED_PIC) for accuracy before starting the install with the command: make install arch=NON_THREADED_PIC Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- config.c.orig Tue Jul 1 12:35:09 2003 |+++ config.c Tue Jul 1 12:35:44 2003 -------------------------- Patching file config.c using Plan A... Hunk #1 succeeded at 81 (offset 2 lines). done gcc -o xconfig config.c /var/tmp//ccUFODCt.o(.text+0x871): In function `CmndResults': : warning: warning: tmpnam() possibly used unsafely; consider using mkstemp() make: illegal option -- - usage: make [-BPSXeiknqrstv] [-C directory] [-D variable] [-d flags] [-E variable] [-f makefile] [-I directory] [-j max_jobs] [-m directory] [-V variable] [variable=value] [target ...] ATLAS3.6.0 configure started. 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 099 098 097 096 095 094 093 092 091 090 089 088 087 086 085 084 083 082 081 080 079 078 077 076 075 074 073 072 071 070 069 068 067 066 065 064 063 062 061 060 059 058 057 056 055 054 053 052 051 050 049 048 047 046 045 044 043 042 041 040 039 038 037 036 035 034 033 032 031 030 029 028 027 026 025 024 023 022 021 020 019 018 017 016 015 014 013 012 011 010 009 008 007 006 005 004 003 002 001 Enter number at top left of screen [0]: =============================================================================== IMPORTANT =============================================================================== Before going any further, check http://math-atlas.sourceforge.net/errata.html This is the ATLAS errata file, which keeps a running count of all known ATLAS bugs and system problems, with associated workarounds or fixes. IF YOU DO NOT CHECK THIS FILE, YOU MAY BE COMPILING A LIBRARY WITH KNOWN BUGS. Have you scoped the errata file? [y]: Configure will ask a series of questions, in one of two forms. The first form of question is a menu of choices. One option in almost all menus is 'Other/UNKNOWN'. If you are unsure of the answer, always choose this option. The second form of question is a single line, with a default answer shown in square braces. If you hit return without typing anything, this default answer will be used. Again, if you are unsure of the answer, simply accept the default. ATLAS can detect almost everything it needs to know, so choosing the default or 'Other/UNKNOWN' will at worst simply extend the install time (if you tell config the answer to something ATLAS can skip some tests). Configure makes no changes to the state of things until all questions have been asked and answered. Therefore, if you get confused and want to start over, feel free to break out of this program (CTRL-C, CTRL-BREAK, etc) and start again. Alternatively, if you make a mistake you can finish the configure process, and then edit the created make include file by hand to fix the mistake manually (the name and location of this file will be printed out at the end of configure). If you have problems during configure or installation, consult the file 'ATLAS/README/TroubleShoot.txt'. Are you ready to continue? [y]: Probing to make operating system determination: Operating system configured as FreeBSD Probing for architecture: Architecture is set to PIII Probing for supported ISA extensions: AltiVec: NO. AltiVec: NO. SSE2: NO. SSE1: DETECTED! Number of CPUs: 1 Looking for compilers (this may take a while): cc : v3.4.4 F77 = /usr/bin/f77 -O -pthread CC = /usr/bin/cc -fomit-frame-pointer -O3 -funroll-all-loops -pthread MCC = /usr/bin/cc -fomit-frame-pointer -O -pthread FINDING tar, gzip, AND gunzip tar : /usr/bin/tar gzip : /usr/bin/gzip gunzip : /usr/bin/gunzip ATLAS has default parameters for OS='FreeBSD' and system='PIII'. If you want to just trust these default values, you can use express setup, drastically reducing the amount of questions you are required to answer use express setup? [y]: You need to choose a name which represents this architecture (eg. UltraSparc, Dec21164, etc). Do not use a generic name (eg. solaris, linux), which might apply to different hardware. This architecture name will be appended to the name of the created make include file, and appear in all subdirectories, so don't make it longer than you like to type. The name should follow the rules for file names (so don't use punctuation and spaces, for instance). <arch> set to 'THREADED' This next value is the size, in kilobytes, that ATLAS must read/write in order to completely flush your largest cache. ATLAS will flush this much memory between timing calls, in order to ensure timings are not inflated by cache preloading. A safe maximum is usually twice the size of your actual largest cache size. If you do not know the size of your largest cache, a maximum value is fine. The only drawback to making this value large is that it requires more memory to do timings, and may slow down the install process (if you have only a small amount of memory, it can also invalidate the timings by causing the timers to swap). The default given below is ATLAS's idea of either the maximum cache your system could have, or the maximum ATLAS believes it is safe to flush. If you are certain that your largest cache is smaller than the default given below, expedite the install by changing it. If you are certain you have enough memory to support the necessary memory demands without swapping, and the value is not twice the size of your largest cache, increase it. Otherwise, just hit enter to continue. Enter Maximum cache size (KB) [512]: The ATLAS install process is heavily file-based, and this can cause major reliability problems when interacting with an overloaded or malfunctioning remotely mounted filesystem. ATLAS therefore has a mechanism in place to allow for a delay before a file is declared to not be there, so that slow NFS (i.e., waiting for amd timout) problems can be overcome, or for handling slightly differing clocks between server/client. This problem is magnified if doing cross-compilation. In the question below, we ask how much of a delay, in seconds, ATLAS should tolerate between file creation and appearance. If you are installing on a local filesystem (eg. /tmp) or a smooth-running NFS system, answer 0; for a moderately loaded NFS server, you may want a value in the 10 second range, and for cross-compiling systems or NFS servers experiencing errors, you may want to go as high as a couple of minutes (120). Enter File creation delay in seconds [0]: I'm going to ask you for information about your Fortran 77 compiler. ATLAS does not need Fortran77 to build, so if you don't have a Fortran compiler, the install can still be completed successfully. However, ATLAS built without a Fortran compiler will not be callable from Fortran (i.e., the user should use the C interface), and we will not be able to do full testing, since some of the tester code is written in Fortran77. F77 & FLAGS: /usr/bin/f77 -O -pthread FLINKER & FLAGS: $(F77) $(F77FLAGS) CC & FLAGS: /usr/bin/cc -fomit-frame-pointer -O3 -funroll-all-loops -pthread MCC & FLAGS: /usr/bin/cc -fomit-frame-pointer -O -pthread CLINKER & FLAGS: $(CC) $(CCFLAGS) Finding F77 to C calling conventions (this may take a while): Calculated F77/C interoperation conventions: Suffix F77 names with underscores with __ F77 INTEGER -> C int F77 strings handled via standard sun style The ATLAS team has provided a default install for your architecture. If you want, these default values can be used, and ATLAS can skip most of the search for your machine. This will greatly decrease the amount of time required for the install, allow you to take advantage of any special features found by the ATLAS team, and provide protection against install miscues caused by unreliable timing results, assuming you really have the machine ATLAS thinks you have. If your machine is non-standard in some way, or you just want to see the ATLAS search for yourself, you should answer no to the following question. Otherwise, it is highly recommended to accept the default of yes. Use supplied default values for install? [y]: Unpacking Architectural defaults . . . done. Your architectural defaults do not include defaults for the Level 1 BLAS. ATLAS now has the ability to tune the Level 1 BLAS to your machine. However, this will add time to the install. If your algorithm utilizes the Level 2 or Level 3 BLAS to any degree, the the Level 1 BLAS will usually be a low order term, and thus only matter for small problems. Therefore, if you don't think you need good performance from the Level 1 BLAS, you can answer "no" to the question below, and ATLAS will skip the Level 1 tuning. ATLAS will still provide Level 1 BLAS, but their performance may be much worse than if tuning were allowed. Tune the Level 1 BLAS? [y]: Creating make include file Make.THREADED Make.THREADED successfully created. Creating ATLrun.sh Creating subdirectories: Checking for already existing subdirectories ........ no Subdirectories successfully created. Moving config logfiles ConfSummary.log and ConfDump.log to bin/THREADED/INSTALL_LOG/ Configuration completed successfully. You may want to examine the make include file (Make.THREADED) for accuracy before starting the install with the command: make install arch=THREADED make: illegal option -- - usage: make [-BPSXeiknqrstv] [-C directory] [-D variable] [-d flags] [-E variable] [-f makefile] [-I directory] [-j max_jobs] [-m directory] [-V variable] [variable=value] [target ...] ATLAS3.6.0 configure started. 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 099 098 097 096 095 094 093 092 091 090 089 088 087 086 085 084 083 082 081 080 079 078 077 076 075 074 073 072 071 070 069 068 067 066 065 064 063 062 061 060 059 058 057 056 055 054 053 052 051 050 049 048 047 046 045 044 043 042 041 040 039 038 037 036 035 034 033 032 031 030 029 028 027 026 025 024 023 022 021 020 019 018 017 016 015 014 013 012 011 010 009 008 007 006 005 004 003 002 001 Enter number at top left of screen [0]: =============================================================================== IMPORTANT =============================================================================== Before going any further, check http://math-atlas.sourceforge.net/errata.html This is the ATLAS errata file, which keeps a running count of all known ATLAS bugs and system problems, with associated workarounds or fixes. IF YOU DO NOT CHECK THIS FILE, YOU MAY BE COMPILING A LIBRARY WITH KNOWN BUGS. Have you scoped the errata file? [y]: Configure will ask a series of questions, in one of two forms. The first form of question is a menu of choices. One option in almost all menus is 'Other/UNKNOWN'. If you are unsure of the answer, always choose this option. The second form of question is a single line, with a default answer shown in square braces. If you hit return without typing anything, this default answer will be used. Again, if you are unsure of the answer, simply accept the default. ATLAS can detect almost everything it needs to know, so choosing the default or 'Other/UNKNOWN' will at worst simply extend the install time (if you tell config the answer to something ATLAS can skip some tests). Configure makes no changes to the state of things until all questions have been asked and answered. Therefore, if you get confused and want to start over, feel free to break out of this program (CTRL-C, CTRL-BREAK, etc) and start again. Alternatively, if you make a mistake you can finish the configure process, and then edit the created make include file by hand to fix the mistake manually (the name and location of this file will be printed out at the end of configure). If you have problems during configure or installation, consult the file 'ATLAS/README/TroubleShoot.txt'. Are you ready to continue? [y]: Probing to make operating system determination: Operating system configured as FreeBSD Probing for architecture: Architecture is set to PIII Probing for supported ISA extensions: AltiVec: NO. AltiVec: NO. SSE2: NO. SSE1: DETECTED! Number of CPUs: 1 Looking for compilers (this may take a while): cc : v3.4.4 F77 = /usr/bin/f77 -fpic -DPIC -O CC = /usr/bin/cc -fomit-frame-pointer -O3 -funroll-all-loops -pthread MCC = /usr/bin/cc -fomit-frame-pointer -O -pthread FINDING tar, gzip, AND gunzip tar : /usr/bin/tar gzip : /usr/bin/gzip gunzip : /usr/bin/gunzip ATLAS has default parameters for OS='FreeBSD' and system='PIII'. If you want to just trust these default values, you can use express setup, drastically reducing the amount of questions you are required to answer use express setup? [y]: You need to choose a name which represents this architecture (eg. UltraSparc, Dec21164, etc). Do not use a generic name (eg. solaris, linux), which might apply to different hardware. This architecture name will be appended to the name of the created make include file, and appear in all subdirectories, so don't make it longer than you like to type. The name should follow the rules for file names (so don't use punctuation and spaces, for instance). <arch> set to 'THREADED_PIC' This next value is the size, in kilobytes, that ATLAS must read/write in order to completely flush your largest cache. ATLAS will flush this much memory between timing calls, in order to ensure timings are not inflated by cache preloading. A safe maximum is usually twice the size of your actual largest cache size. If you do not know the size of your largest cache, a maximum value is fine. The only drawback to making this value large is that it requires more memory to do timings, and may slow down the install process (if you have only a small amount of memory, it can also invalidate the timings by causing the timers to swap). The default given below is ATLAS's idea of either the maximum cache your system could have, or the maximum ATLAS believes it is safe to flush. If you are certain that your largest cache is smaller than the default given below, expedite the install by changing it. If you are certain you have enough memory to support the necessary memory demands without swapping, and the value is not twice the size of your largest cache, increase it. Otherwise, just hit enter to continue. Enter Maximum cache size (KB) [512]: The ATLAS install process is heavily file-based, and this can cause major reliability problems when interacting with an overloaded or malfunctioning remotely mounted filesystem. ATLAS therefore has a mechanism in place to allow for a delay before a file is declared to not be there, so that slow NFS (i.e., waiting for amd timout) problems can be overcome, or for handling slightly differing clocks between server/client. This problem is magnified if doing cross-compilation. In the question below, we ask how much of a delay, in seconds, ATLAS should tolerate between file creation and appearance. If you are installing on a local filesystem (eg. /tmp) or a smooth-running NFS system, answer 0; for a moderately loaded NFS server, you may want a value in the 10 second range, and for cross-compiling systems or NFS servers experiencing errors, you may want to go as high as a couple of minutes (120). Enter File creation delay in seconds [0]: I'm going to ask you for information about your Fortran 77 compiler. ATLAS does not need Fortran77 to build, so if you don't have a Fortran compiler, the install can still be completed successfully. However, ATLAS built without a Fortran compiler will not be callable from Fortran (i.e., the user should use the C interface), and we will not be able to do full testing, since some of the tester code is written in Fortran77. F77 & FLAGS: /usr/bin/f77 -fpic -DPIC -O FLINKER & FLAGS: $(F77) $(F77FLAGS) CC & FLAGS: /usr/bin/cc -fomit-frame-pointer -O3 -funroll-all-loops -pthread MCC & FLAGS: /usr/bin/cc -fomit-frame-pointer -O -pthread CLINKER & FLAGS: $(CC) $(CCFLAGS) Finding F77 to C calling conventions (this may take a while): Calculated F77/C interoperation conventions: Suffix F77 names with underscores with __ F77 INTEGER -> C int F77 strings handled via standard sun style The ATLAS team has provided a default install for your architecture. If you want, these default values can be used, and ATLAS can skip most of the search for your machine. This will greatly decrease the amount of time required for the install, allow you to take advantage of any special features found by the ATLAS team, and provide protection against install miscues caused by unreliable timing results, assuming you really have the machine ATLAS thinks you have. If your machine is non-standard in some way, or you just want to see the ATLAS search for yourself, you should answer no to the following question. Otherwise, it is highly recommended to accept the default of yes. Use supplied default values for install? [y]: Unpacking Architectural defaults . . . done. Your architectural defaults do not include defaults for the Level 1 BLAS. ATLAS now has the ability to tune the Level 1 BLAS to your machine. However, this will add time to the install. If your algorithm utilizes the Level 2 or Level 3 BLAS to any degree, the the Level 1 BLAS will usually be a low order term, and thus only matter for small problems. Therefore, if you don't think you need good performance from the Level 1 BLAS, you can answer "no" to the question below, and ATLAS will skip the Level 1 tuning. ATLAS will still provide Level 1 BLAS, but their performance may be much worse than if tuning were allowed. Tune the Level 1 BLAS? [y]: Creating make include file Make.THREADED_PIC Make.THREADED_PIC successfully created. Creating ATLrun.sh Creating subdirectories: Checking for already existing subdirectories ........ no Subdirectories successfully created. Moving config logfiles ConfSummary.log and ConfDump.log to bin/THREADED_PIC/INSTALL_LOG/ Configuration completed successfully. You may want to examine the make include file (Make.THREADED_PIC) for accuracy before starting the install with the command: make install arch=THREADED_PIC ===> Building for atlas-3.6.0,1 ===> Extracting lapack sub project You can override FC and FFLAGS on the command line. Set ENABLE_TESTING to YES to enable testing and timing. ===> Extracting for lapack-3.0_1 => MD5 Checksum OK for lapack/lapack.tgz. => SHA256 Checksum OK for lapack/lapack.tgz. => MD5 Checksum OK for lapack/manpages.tgz. => SHA256 Checksum OK for lapack/manpages.tgz. ===> Patching for lapack-3.0_1 ===> Applying FreeBSD patches for lapack-3.0_1 ===> lapack-3.0_1 depends on shared library: blas.1 - found ===> Configuring for lapack-3.0_1 ===> Building for lapack-3.0_1 ( cd INSTALL; make; ./testlsame; ./testslamch; ./testdlamch; ./testsecond; ./testdsecnd; cp lsame.f ../BLAS/SRC/; cp lsame.f ../SRC; cp slamch.f ../SRC/; cp dlamch.f ../SRC/; cp second.f ../SRC/; cp dsecnd.f ../SRC/; cp etime_.c ../SRC/ ) f77 -O -mtune= -pipe -O2 -ffast-math -fomit-frame-pointer -c lsame.f lsame.f:0: error: bad value () for -mtune= switch *** Error code 1 Stop in /usr/ports/math/atlas/work/lapack/work/LAPACK/INSTALL. *** Error code 1 Stop in /usr/ports/math/atlas/work/lapack/work/LAPACK. *** Error code 1 Stop in /usr/ports/math/atlas/work/lapack. *** Error code 1 Stop in /usr/ports/math/atlas. >How-To-Repeat: # cd /usr/port/math/atlas # make WITH_OPTIMIZED_OPTION=yes install clean >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200607281626.k6SGQiNi087227>