From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Building lapack failed
Date: Fri, 6 Oct 2006 10:49:56 +0200 [thread overview]
Message-ID: <200610061050.01719.bo.andresen@zlin.dk> (raw)
In-Reply-To: <20061006070513.9603.qmail@web86915.mail.ukl.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]
On Friday 06 October 2006 09:05, JC Denton wrote:
> I try to install lapack on my machine.
>
> This is what I get when I try to emerge lapack:
[SNIP]
> !!! ERROR: sci-libs/lapack-3.0 failed.
[SNIP]
I think bug #146448 [1] is the most relevant bug (which you should be able to
find on your own). Unfortunately it provides no solutions. This package
simply isn't prepared for gcc-4.x yet.
> I had problems with blas before, because I could not find g77 on my system
> but I fixed this by writing a shell script called g77 that points to
> "/usr/lib/R/bin/f77". So blas did compile but now lapack fails.
>
> What can I do about this?
Apologize my ignorance... Why do you need this package anyway? No package
currently in the tree depend on sci-libs/lapack...
[1] https://bugs.gentoo.org/show_bug.cgi?id=146448
....
Hmm.... actually this seems to work for me:
# echo -e '#!/bin/sh\ngfortran -ff2c' > /usr/bin/g77 && chmod +x /usr/bin/g77
# emerge -va sci-libs/lapack
# rm /usr/bin/g77
I strongly suggest that you remove it when you're done since this isn't the
supported solution. At the very least mention it if you ever file a bug where
it might have an impact...
--
Bo Andresen
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-06 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 7:05 [gentoo-user] Building lapack failed JC Denton
2006-10-06 8:49 ` Bo Ørsted Andresen [this message]
2006-10-06 10:50 ` Bo Ørsted Andresen
2006-10-10 20:48 ` JC Denton
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=200610061050.01719.bo.andresen@zlin.dk \
--to=bo.andresen@zlin.dk \
--cc=gentoo-user@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