all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Preliminary MIPS N32 port now available
Date: Fri, 18 Oct 2013 16:01:39 -0400	[thread overview]
Message-ID: <87sivyl55o.fsf@netris.org> (raw)
In-Reply-To: <87bo2mjyzw.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 18 Oct 2013 19:00:03 +0200")

Hi Andreas and Ludovic!

ludo@gnu.org (Ludovic Courtès) writes:

> Andreas Enge <andreas@enge.fr> skribis:
>
>> Personally, I think mips64el should be a fully qualified release architecture
>> just as i686 and x86_64. So it would be better to have it in master and
>> not in a separate branch.
>>
>> So far, the only machines of this architecture available (and of interest)
>> to developers are loongson.
>
> I agree.  Let’s not go ahead of ourselves: when someone comes up with a
> plan to use Guix on a mips64el machine that is not Loongson, then we can
> adapt (and it’s great that you know about all these Loongson workarounds.)

Okay, sounds good.  However, since it takes me over a week to rebuild
even a basic system after a core package has changed, I need to start by
building on a more stable base.  That will allow me to find problems
higher up in the software stack and apply patches as needed.

In the meantime, feel free to apply any commits from the "loongson"
branch to core-updates.  The current set of commits should be fine, but
later on, I'll probably push some things to "loongson" that you won't
want in master.  It would be nice if all of the important Loongson
patches were ready to send upstream, but unfortunately many of them are
not.

So while I certainly agree that the ultimate goal should be to
eventually eliminate the "loongson" branch, I expect it will be some
time before we can do that.

      Mark

  reply	other threads:[~2013-10-18 20:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18  3:19 Preliminary MIPS N32 port now available Mark H Weaver
2013-10-18  8:26 ` Andreas Enge
2013-10-18 15:41   ` Mark H Weaver
2013-10-18 16:37     ` Andreas Enge
2013-10-18 17:00       ` Ludovic Courtès
2013-10-18 20:01         ` Mark H Weaver [this message]
2013-10-18 20:50           ` Ludovic Courtès
2013-10-18  8:28 ` Nikita Karetnikov
2013-10-19  2:28   ` Nikita Karetnikov
2013-10-19  3:03     ` Mark H Weaver
2013-10-19  3:25       ` Mark H Weaver
2013-10-19  3:45         ` Nikita Karetnikov
2013-10-20  0:44           ` Nikita Karetnikov
2013-10-20 17:45             ` Mark H Weaver
2013-10-19  3:35       ` Nikita Karetnikov
2013-10-18 16:14 ` Ludovic Courtès
2013-10-19 18:58 ` Preliminary MIPS N32 port: IMPORTANT CAVEAT Mark H Weaver
2013-10-26 20:31   ` Ludovic Courtès
2013-10-23  5:11 ` Important libffi bug fix for MIPS N32 Mark H Weaver
2013-10-23  6:00   ` Nikita Karetnikov
2013-10-23  6:50     ` Mark H Weaver
2013-10-23 16:40       ` Nikita Karetnikov
2013-10-23 17:43         ` Mark H Weaver
2013-10-26 20:41         ` Ludovic Courtès
2013-10-27 20:20           ` Nikita Karetnikov
2013-10-28 13:08             ` Ludovic Courtès
2013-10-23 11:58   ` Andreas Enge
2013-10-23 18:32     ` Mark H Weaver
2013-10-27  4:00       ` Mark H Weaver

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=87sivyl55o.fsf@netris.org \
    --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.