[gentoo-user-br] emerge blas-atlas falha

[Júlio Cesar Bueno Cotta]

pois entao galera

eu mandei dar um emerge scilab na maquina aqui deu erro
mandou eu dar um " interactive=1 emerge blas-atlas   "

mas ai eu tenho que entrar com ums dados ...mas esta dando erro


a maquian eh um pentium D 930

o instalador  me faz umas perguntas vou postar aqui

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]: 160

===============================================================================
                                  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]: 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/doc/TroubleShoot.txt'.

Are you ready to continue? [y]: y
Probing to make operating system determination:
Operating system configured as Linux

archinfo_x86.c: In function 'PrintUsage':
archinfo_x86.c:106: warning: incompatible implicit declaration of built-in
function 'exit'
archinfo_x86.c: In function 'main':
archinfo_x86.c:211: warning: incompatible implicit declaration of built-in
function 'exit'
make[2]: *** [atlas_run] Error 11
make[1]: *** [IRunx8664] Error 2
Probing for architecture:
make[2]: *** [atlas_run] Error 11
make[1]: *** [IRunx86Info] Error 2
Enter your machine type:
   1. Other/UNKNOWN
   2. AMD Athlon
   3. 32 bit AMD Hammer
   4. 64 bit AMD Hammer
   5. Pentium PRO
   6. Pentium II
   7. Pentium III
   8. Pentium 4
   9. Pentium 4E (prescott)
  10. Transmeta Efficeon
Enter machine number [1]: 9
Architecture is set to P4E


Probing for supported ISA extensions:
   AltiVec: NO.
   AltiVec: NO.
   SSE3: DETECTED!

ATLAS can provide SMP support for the Level 3 BLAS via Posix threads.
If you choose to build a threaded library, ATLAS will compile all
aspects of the library (including the serial components) with the
threaded compiler/link flags.  Most machines can use the serial
library even when it is compiled with threaded options, but this
is not guaranteed to work, so if you want a true serial library,
answer no to threading below.
   enable Posix threads support? [y]: y
Number of CPUs: 2

Looking for compilers (this may take a while):
   /usr/bin/gcc  : v4.1.1
F77 = /usr/i686-pc-linux-gnu/gcc-bin/4.1.1/gfortran -O
CC = /usr/bin/gcc -fomit-frame-pointer -O3 -funroll-all-loops
MCC = /usr/bin/gcc -fomit-frame-pointer -O

FINDING tar, gzip, AND gunzip
   tar    : /bin/tar
   gzip   : /bin/gzip
   gunzip : /bin/gunzip


ATLAS has default parameters for OS='Linux' and system='P4E'.
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]: 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).

   Enter Architecture name (ARCH) [Linux_P4ESSE3_2]:
<arch> set to 'Linux_P4ESSE3_2'



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) [1024]:y

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]: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/i686-pc-linux-gnu/gcc-bin/4.1.1/gfortran -O
FLINKER & FLAGS: $(F77) $(F77FLAGS)

CC & FLAGS: /usr/bin/gcc -fomit-frame-pointer -O3 -funroll-all-loops
MCC & FLAGS: /usr/bin/gcc -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 _
   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]:y



-- 
        julio Cesar Bueno Cotta
Graduando em ciência da computação
    Universidade Federal de Viçosa