From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sci-libs/{amd,camd}-2.4.6/ doc wierdness
Date: Wed, 16 Dec 2020 20:02:31 -0500 [thread overview]
Message-ID: <7cdce263-f75f-57df-d276-796962997af3@gentoo.org> (raw)
In-Reply-To: <20201216221643.2B58182CBBF6@turkos.aspodata.se>
On 12/16/20 5:16 PM, karl@aspodata.se wrote:
>
> It will probably, cannot test just now, rust is compiling....
>
I'm sorry for your loss. I opened
https://bugs.gentoo.org/760408
to track this issue, but we will probably hack around it in the ebuild
for now. Our SuiteSparse ebuilds are far behind the upstream versions
and had their autotools build system patched in, at a time when the
upstream build system was junk.
Nowadays upstream is using CMake, so it makes more sense to upgrade and
switch to CMake than it does to try to fix the evolutionary-dead-end
autotools patches.
next prev parent reply other threads:[~2020-12-17 1:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 17:30 [gentoo-user] sci-libs/{amd,camd}-2.4.6/ doc wierdness karl
2020-12-16 18:17 ` Michael Orlitzky
2020-12-16 18:29 ` Michael Orlitzky
2020-12-16 22:16 ` karl
2020-12-17 1:02 ` Michael Orlitzky [this message]
2020-12-17 19:16 ` karl
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=7cdce263-f75f-57df-d276-796962997af3@gentoo.org \
--to=mjo@gentoo.org \
--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