From: Nils Gillmann <ng0@n0.is>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 31955@debbugs.gnu.org, "Clément Lassieur" <clement@lassieur.org>,
"Nils Gillmann" <ng0@n0.is>
Subject: [bug#31955] [PATCH] gnu: rust: support build with glibc-2.27, update to 1.26.2
Date: Wed, 11 Jul 2018 06:06:05 +0000 [thread overview]
Message-ID: <20180711060605.dauclmyphyywo2f5@abyayala> (raw)
In-Reply-To: <3f9d226e-abfc-0129-6ac1-466f368d88ce@web.de>
Jonathan Brielmaier transcribed 319 bytes:
> On 7/7/18 10:13 PM, Nikolai Merinov wrote:
> > Hi Danny,
> >
> > Thank you! I was able to reproduce issue locally. I started
> > investigation.
> >
> > Regards,
> > Nikolai
> >
>
> Hallo Nikolai,
>
> I think you forgot to add those two patches
> rust-bootstrap-stage0-test.patch
> rust-coresimd-doctest.patch
> to gnu/lokal.mk...
>
> Jonathan
>
>
>
>
Is there a problem with the pathc thath got commited?
I've been trying to build the new version to no avail.
I almost got to the new version but then the process
hang. Restarting the build now only lead to a night long
building of the very first version with no success of
even finishing that.
prev parent reply other threads:[~2018-07-11 6:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 21:34 [bug#31955] [PATCH] gnu: rust: support build with glibc-2.27, update to 1.26.2 Nikolai Merinov
2018-06-27 10:06 ` Jelle Licht
2018-07-02 15:28 ` Ludovic Courtès
2018-07-04 9:31 ` Nils Gillmann
2018-07-04 9:47 ` Clément Lassieur
2018-07-04 12:39 ` Nikolai Merinov
2018-07-04 15:45 ` Danny Milosavljevic
2018-07-04 22:07 ` Nikolai Merinov
2018-07-07 7:09 ` Danny Milosavljevic
2018-07-07 14:53 ` Ludovic Courtès
2018-07-09 14:23 ` Danny Milosavljevic
2018-07-07 20:13 ` Nikolai Merinov
2018-07-10 15:54 ` Jonathan Brielmaier
2018-07-11 6:06 ` Nils Gillmann [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=20180711060605.dauclmyphyywo2f5@abyayala \
--to=ng0@n0.is \
--cc=31955@debbugs.gnu.org \
--cc=clement@lassieur.org \
--cc=jonathan.brielmaier@web.de \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.