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 12:50:25 +0200 [thread overview]
Message-ID: <200610061250.31607.bo.andresen@zlin.dk> (raw)
In-Reply-To: <200610061050.01719.bo.andresen@zlin.dk>
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
On Friday 06 October 2006 10:49, Bo Ørsted Andresen wrote:
> 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.
[SNIP]
> [1] https://bugs.gentoo.org/show_bug.cgi?id=146448
As you can read on the bug those packages are deprecated. Still I've made a
couple of patches (attached on the bug) that makes it compile with
gfortran... (The eclasses really do all the work...)
--
Bo Andresen
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-06 10:56 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
2006-10-06 10:50 ` Bo Ørsted Andresen [this message]
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=200610061250.31607.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