From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: core-updates frozen
Date: Mon, 16 Jun 2014 11:19:59 -0400 [thread overview]
Message-ID: <8738f42868.fsf@yeeloong.lan> (raw)
In-Reply-To: <87r42pfgf8.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 16 Jun 2014 09:43:23 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> I'm sorry I haven't had time to look into this, but in April I tried to
>> build GCC 4.9.0 on my YeeLoong and it failed.
>
> That doesn’t look Guix-specific, no?
No, it doesn't.
>> Unless it has been fixed since then, this might mean that our MIPS
>> port will be non-functional in the next release.
>
> No, because we use 4.8.3 in the build environment.
Ah, good.
> Unfortunately, the MIPS box for Hydra is currently off-line, so I don’t
> have any feedback. It would be great if you could start building the
> branch.
Okay, I'll start a build and let you know.
Thanks,
Mark
next prev parent reply other threads:[~2014-06-16 15:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 6:51 core-updates is back Ludovic Courtès
2014-04-15 7:45 ` gmp-6.0.0a Andreas Enge
2014-04-15 9:37 ` gmp-6.0.0a Ludovic Courtès
2014-04-15 9:46 ` gmp-6.0.0a Andreas Enge
2014-04-15 15:36 ` gmp-6.0.0a Ludovic Courtès
2014-04-16 6:15 ` gmp-6.0.0a Andreas Enge
2014-06-06 13:33 ` core-updates is back Ludovic Courtès
2014-06-15 10:08 ` core-updates frozen Ludovic Courtès
2014-06-15 20:25 ` Ludovic Courtès
2014-06-16 0:47 ` Mark H Weaver
2014-06-16 7:43 ` Ludovic Courtès
2014-06-16 15:19 ` Mark H Weaver [this message]
2014-06-18 16:39 ` Mark H Weaver
2014-06-18 17:03 ` Mark H Weaver
2014-06-18 20:23 ` Ludovic Courtès
2014-06-18 20:42 ` Ludovic Courtès
2014-06-20 21:50 ` Ludovic Courtès
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=8738f42868.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
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.