public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markus Dittrich <markusle@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] status of lapack install
Date: Mon, 19 Mar 2007 21:00:03 +0000 (UTC)	[thread overview]
Message-ID: <Pine.LNX.4.64.0703192051060.4625@woodpecker.gentoo.org> (raw)
In-Reply-To: <D2D7D9FE2492524A925313E2D82E1B5304CCF89F@ORNLEXCHANGE.ornl.gov>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 19 Mar 2007, de Almeida, Valmor F. wrote:
>
> Hello,
> Calculating dependencies... done!
> [ebuild  N    ] sci-libs/lapack-config-1.0.1  0 kB
> [ebuild  N    ] sci-libs/blas-atlas-3.7.11  USE="doc -debug" 1,991 kB
> [ebuild  N    ] sci-libs/lapack-reference-3.0-r1  USE="-debug -ifc"
> 4,935 kB
>

The currently stable lapack-atlas and blas-atlas (3.7.11) compile
fine with gcc-4.x.
Should you go with lapack-reference you will need the most
recent lapack-reference-3.1.1 not lapack-reference-3.0-r1. 
The reference ebuilds (both lapack and blas) take less time
to compile but provide less optimized routines. Hence, you have
to decide what is more important to you.

cheers,
Markus


- -- 
Markus Dittrich (markusle)
Gentoo Linux Developer
Scientific applications
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF/vnVxlRwCwb7k40RAs+dAJ0RRCkPvaDrM7Mq9fS0Iw+hrUddqACeJg7z
YcfVtOwjkn+t4mBHZRfnBrM=
=5Zd7
-----END PGP SIGNATURE-----
-- 
gentoo-science@gentoo.org mailing list



  parent reply	other threads:[~2007-03-19 21:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19 20:17 [gentoo-science] status of lapack install de Almeida, Valmor F.
2007-03-19 20:41 ` Adam Piątyszek
2007-03-19 21:26   ` de Almeida, Valmor F.
2007-03-19 21:00 ` Markus Dittrich [this message]
2007-03-19 21:30   ` de Almeida, Valmor F.
2007-03-19 22:16     ` Markus Dittrich
2007-03-20 14:15       ` de Almeida, Valmor F.

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=Pine.LNX.4.64.0703192051060.4625@woodpecker.gentoo.org \
    --to=markusle@gentoo.org \
    --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