From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: Preliminary MIPS N32 port now available Date: Fri, 18 Oct 2013 16:01:39 -0400 Message-ID: <87sivyl55o.fsf@netris.org> References: <871u3jmfkp.fsf@netris.org> <20131018082616.GA4815@debian.eduroam.u-bordeaux.fr> <87wqlalh7f.fsf@netris.org> <20131018163746.GA7139@debian.eduroam.u-bordeaux.fr> <87bo2mjyzw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36676) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VXGG6-0002kj-FU for guix-devel@gnu.org; Fri, 18 Oct 2013 16:02:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VXGG1-0001VC-4s for guix-devel@gnu.org; Fri, 18 Oct 2013 16:02:54 -0400 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") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org Hi Andreas and Ludovic! ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Andreas Enge skribis: > >> Personally, I think mips64el should be a fully qualified release archite= cture >> 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 interes= t) >> to developers are loongson. > > I agree. Let=E2=80=99s 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=E2=80=99s great that you know about all these Loongson work= arounds.) 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