From: "Gábor Boskovits" <boskovits@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>, 36685@debbugs.gnu.org
Subject: Re: bug#36685: ant-bootstrap fails on core-updates (409 dependents)
Date: Sun, 21 Jul 2019 17:57:35 +0200 [thread overview]
Message-ID: <CAE4v=phrw3vh9Y0vF4wV0Lmir4pmH6OwUTTPiMnaoi=dd6nD+A@mail.gmail.com> (raw)
In-Reply-To: <87muh7eid5.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
Hello,
Ricardo Wurmus <rekado@elephly.net> ezt írta (időpont: 2019. júl. 21., Vas
13:29):
> So, with the following change I was able to build all the way up to the
> latest openjdk. Should we use it despite the introduction of a memory
> leak in a bootstrap JVM? Can we make the patch smaller (fewer uses of
> glibc 2.28 or gcc-5)?
>
> What do you think?
>
I will have a look at reducing the patch later today. I will report back
tomorrow morning with the results.
>
> --
> Ricardo
>
[-- Attachment #2: Type: text/html, Size: 1040 bytes --]
next prev parent reply other threads:[~2019-07-21 15:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8736j61n57.fsf@gmail.com>
[not found] ` <87o91ugdot.fsf@elephly.net>
[not found] ` <87ftn5gjzw.fsf@elephly.net>
[not found] ` <871ryogu6j.fsf@elephly.net>
2019-07-18 10:51 ` bug#36685: ant-bootstrap fails on core-updates (409 dependents) Ricardo Wurmus
2019-07-18 11:09 ` Efraim Flashner
2019-07-21 17:44 ` Ricardo Wurmus
2019-07-19 8:09 ` Ricardo Wurmus
2019-07-19 12:37 ` Gábor Boskovits
2019-07-19 12:56 ` Ricardo Wurmus
2019-07-19 16:30 ` Ricardo Wurmus
2019-07-20 8:42 ` Ricardo Wurmus
2019-07-20 9:06 ` Julien Lepiller
2019-07-20 21:07 ` Ricardo Wurmus
2019-07-21 11:29 ` Ricardo Wurmus
2019-07-21 15:57 ` Gábor Boskovits [this message]
2019-07-24 21:07 ` Ricardo Wurmus
2019-09-06 13:40 ` Ricardo Wurmus
2019-09-06 13:41 ` Gábor Boskovits
2019-09-07 14:28 ` Ricardo Wurmus
2019-09-07 15:01 ` Julien Lepiller
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=phrw3vh9Y0vF4wV0Lmir4pmH6OwUTTPiMnaoi=dd6nD+A@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=36685@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).