I'm having problems emerging blas-atlas-3.6.0-r1 on my AMD64 X2 system.
The configure drops into an infinite loop :
I am now going to ask for two C compilers, and their associated flags.
The first such set (CC & CCFLAGS) are used in compiling the
non-generated
ATLAS code. This code is written in normal C, and responds well to high
levels of optimization. Typically, this is set to your default
compiler,
and your highest levels of optimization.
The second set of C compilers (MCC & MMFLAGS) is used to compile the
generated
ATLAS code. Generated codes are written at a very low-level (think of
C used
as a kind of portable assembler). On many platforms, high levels of
optimization are detrimental, as the compiler tries to pipeline a
perfectly
pipelined code, and succeeds in reducing performance substantially (this
occurs on DEC ALPHAs & Sun UltraSparcs, for instance). If the default
does
not work for you, try a midrange optimization such as -O. The
generated code
does not alias any output arguments, so aliasing optimizations should
be OK.
Enter ANSI C compiler(CC) [/usr/bin/gcc]: Enter C Flags (CCFLAGS)
[-fomit-frame-pointer -O -mfpmath=387 -m64]: Compiling with = '/usr/bin/gcc
-fomit-frame-pointer -O -mfpmath=387 -m64' doesn't seem to work for me.
Enter 1 to try different CC/flags, 0 to continue anyway [1]:
I've turned in a bugzilla ticket - but I thought someone here might have
a suggestion for my platform. Is there a compiler flag I should set that
would make it happy? Mine are pretty simple : CFLAGS="-O2 -march=athlon-xp"
This is a brand new system, so all the ebuilds from the kernel up are completely
current.
--
-----------------------------------------------------------------------
| Alan K. Jackson | To see a World in a Grain of Sand |
| [EMAIL PROTECTED] | And a Heaven in a Wild Flower, |
| www.ajackson.org | Hold Infinity in the palm of your hand |
| Houston, Texas | And Eternity in an hour. - Blake |
-----------------------------------------------------------------------
--
[email protected] mailing list
