From: David Haller <gentoo@dhaller.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sci-libs/spqr-1.2.3-r1 failed to emerge
Date: Thu, 9 Apr 2020 06:28:08 +0200 [thread overview]
Message-ID: <20200409042808.433aekvbzj3nem2q@grusum.endjinn.de> (raw)
In-Reply-To: <CA+t6X7eu4p=iNogTL0uSoMf1RjDXbi5Ou3FNoq1fJifa7J4S+w@mail.gmail.com>
Hello,
On Wed, 08 Apr 2020, gevisz wrote:
>I've tried to install julia-1.4.0 but one of its dependencies, namely,
>sci-libs/spqr-1.2.3-r1 failed to emerge with the following error message:
>
>* Failed Running automake !
> *
> * Include in your bugreport the contents of:
> *
> * /var/tmp/portage/sci-libs/spqr-1.2.3-r1/temp/automake.out
The patch spqr-1.2.3-autotools.patch is broken, it includes two
AM_INIT_AUTOMAKE lines in configure.ac:
====
[..]
--- configure.ac 1969-12-31 19:00:00.000000000 -0500
+++ configure.ac 2009-10-22 23:42:32.000000000 -0400
@@ -0,0 +1,55 @@
+AC_PREREQ(2.59)
+AC_INIT(spqr, 1.2, davis@cise.ufl.edu)
+AM_INIT_AUTOMAKE([foreign])
+AC_CONFIG_SRCDIR([Source/spqr_kernel.cpp])
+AM_INIT_AUTOMAKE([foreign])
[..]
====
Deleting the first (and adjusting the patchlength: '@@ -0,0 +1,54 @@')
and it works.
HTH,
-dnh
--
> Write the code like you are going to lose your memory in six months.
Most people would say I write code like I've already lost my mind.
Is that the same thing? -- Randal L. Schwartz
prev parent reply other threads:[~2020-04-09 21:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 10:37 [gentoo-user] sci-libs/spqr-1.2.3-r1 failed to emerge gevisz
2020-04-08 10:29 ` [gentoo-user] " Nuno Silva
2020-04-08 14:19 ` gevisz
2020-04-08 14:45 ` gevisz
2020-04-08 13:00 ` Neil Bothwick
2020-04-08 15:01 ` gevisz
2020-04-08 15:12 ` Michael Orlitzky
2020-04-08 16:31 ` gevisz
2020-04-09 6:49 ` gevisz
2020-04-09 7:32 ` Nuno Silva
2020-04-09 11:46 ` gevisz
2020-04-09 13:19 ` gevisz
2020-04-09 4:28 ` David Haller [this message]
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=20200409042808.433aekvbzj3nem2q@grusum.endjinn.de \
--to=gentoo@dhaller.de \
--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