From: grozin@gentoo.org
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev-announce] Call for agenda items - Council meeting 2018-12-09
Date: Sun, 2 Dec 2018 16:30:54 +0700 (+07) [thread overview]
Message-ID: <alpine.LRH.2.21.1812021622070.35092@star.inp.nsk.su> (raw)
In-Reply-To: <2a393e89-3156-9666-de46-2faf2fd1f7e3@gentoo.org>
On Sat, 1 Dec 2018, Mikle Kolyada wrote:
> 13.0 profiles removal, 17,0 set was added a year ago, and even arm has
> been migrated successfully.
dev-lisp/clozurecl is broken in 17.0. On ~x86 compiling it loops forever.
I heard that on ~amd64 it compiles but the resulting binary is broken: it
fails to compile maxima. The upstream says that this is related to Gentoo
specific compilation options, and they recommend to use the upstream
options. In 13.0 clozurecl works fine.
I think those who introduced 17.0 should fix what they have broken. I use
13.0, and cannot switch so far.
Andrey Grozin
next prev parent reply other threads:[~2018-12-02 9:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 12:31 [gentoo-project] Call for agenda items - Council meeting 2018-12-09 Mart Raudsepp
2018-11-30 16:17 ` William Hubbs
2018-11-30 16:24 ` Alec Warner
2018-12-06 17:32 ` William Hubbs
2018-12-01 7:47 ` [gentoo-project] Re: [gentoo-dev-announce] " Mikle Kolyada
2018-12-02 9:30 ` grozin [this message]
2018-12-02 15:55 ` Michał Górny
2018-12-02 16:06 ` Michał Górny
2018-12-04 0:16 ` Aaron Bauman
2018-12-04 0:39 ` M. J. Everitt
2018-12-04 1:29 ` Aaron Bauman
2018-12-04 3:41 ` Michał Górny
2018-12-04 9:54 ` Kristian Fiskerstrand
2018-12-04 10:06 ` Mart Raudsepp
2018-12-04 21:18 ` Aaron Bauman
2018-12-04 22:51 ` Sergei Trofimovich
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=alpine.LRH.2.21.1812021622070.35092@star.inp.nsk.su \
--to=grozin@gentoo.org \
--cc=gentoo-project@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