From: Alan Jackson <ajackson@oplnk.net>
To: gentoo-science@lists.gentoo.org
Subject: [gentoo-science] Problems emerging blas-atlas
Date: Sun, 5 Feb 2006 14:23:44 -0600 [thread overview]
Message-ID: <20060205142344.4f1d694e.ajackson@oplnk.net> (raw)
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 |
| alan@ajackson.org | 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 |
-----------------------------------------------------------------------
--
gentoo-science@gentoo.org mailing list
next reply other threads:[~2006-02-05 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-05 20:23 Alan Jackson [this message]
2006-02-05 21:57 ` [gentoo-science] Problems emerging blas-atlas Jason Nielsen
2006-02-06 1:51 ` Alan Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060205142344.4f1d694e.ajackson@oplnk.net \
--to=ajackson@oplnk.net \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox