public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: "François Bissey" <fbissey@slingshot.co.nz>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] BLAS and LAPACK dependecy resolution
Date: Thu, 12 Sep 2013 11:58:10 +1200	[thread overview]
Message-ID: <852d59ca17ead8a1bddc9f6b6ab0047d@slingshot.co.nz> (raw)
In-Reply-To: <874n9rhull.wl%oehme.markus@gmx.de>

On 2013-09-12 10:16, Markus Oehme wrote:
> Hi everybody,
> 
> every time I touch anything realted to blas and lapack it blows up in 
> my
> face. I just did a fresh install on my computer and I'm getting all 
> sorts of
> 'cannot find blas' and 'cannot find lapack' (hence currently no sage 
> for me
> since half it dependencies don't build). Is there some documentation as 
> to
> how to sort this mess out?
> 
> Even more fun: I'm currently unable to install eselect::science (which 
> is as
> I understand it necessary to flee the above mentioned hell), since
> eselect-bashcomp requires >=eselect-1.3.8.
> 
> I'm even annoyed enough that I think I could devote some time to 
> helping to
> make an end to this snafu -- if somebody points out, how. (My first 
> guess
> is, that it would reduce the clusterfuck potential if the science 
> overlay
> and main tree machinery [eselect::science I'm looking at you], could be
> synced again).
> 
My first step to solve problems is to mask
app-admin/eselect::gentoo
Second we should maintain and distribute a package.keywords list
for the blas/lapack stack, we could alternative distribute a 
package.mask
for the main tree blas/lapack stack.
Bear in mind that we cannot mask the main tree blas/lapack stack from
the overlay's profile. Such a package.mask only affects the overlay.
So in any case you will need to explicitly copy or link to a provided
file (whether it is a mask or a keyword file).

Francois





  parent reply	other threads:[~2013-09-11 23:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 22:16 [gentoo-science] BLAS and LAPACK dependecy resolution Markus Oehme
2013-09-11 23:49 ` Horea Christian
2013-09-11 23:58 ` François Bissey [this message]
2013-09-12  0:26   ` François Bissey
2013-09-12  9:19     ` Markus Oehme
2013-09-12  9:39       ` Francois Bissey
2013-09-12 12:52         ` Markus Oehme
2013-09-13  0:22           ` François Bissey
2013-09-14  8:14       ` Markus Oehme
2013-09-14  9:33         ` Francois Bissey
2013-09-14 11:29           ` Markus Oehme
2013-09-26 22:43             ` Wiki stuff (was: [gentoo-science] BLAS and LAPACK dependecy resolution) Markus Oehme
2013-10-29 10:33 ` [gentoo-science] BLAS and LAPACK dependecy resolution Markus Oehme

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=852d59ca17ead8a1bddc9f6b6ab0047d@slingshot.co.nz \
    --to=fbissey@slingshot.co.nz \
    --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