All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Laurent GUERBY <laurent@guerby.net>
Cc: Jon Fraser <jfraser@broadcom.com>,
	Andrew Wiley <debio264@gmail.com>,
	"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
	"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: Bigsur?
Date: Tue, 19 May 2009 13:53:10 +0100	[thread overview]
Message-ID: <20090519125310.GA17733@linux-mips.org> (raw)
In-Reply-To: <1242735440.6098.101.camel@localhost>

On Tue, May 19, 2009 at 02:17:20PM +0200, Laurent GUERBY wrote:

> On Mon, 2009-05-18 at 23:47 +0100, Maciej W. Rozycki wrote:
> >  Yes, invaluable for native builds and there is a considerable number of 
> > software packages which is not capable of being cross-compiled, or 
> > requires extreme contortions to be built this way, or if buildable with a 
> > reasonable effort, the functionality is limited.  Besides a three-stage 
> > GCC bootstrap is a good way of verifying the quality of the tool, never 
> > mind standard DejaGNU-based regression testing which although possible 
> > using cross-tools and a remote target, is awfully painful to be set up 
> > this way.
> 
> For MIPS in the GCC Compile Farm http://gcc.gnu.org/wiki/CompileFarm
> (which is open to all free software, not limited to GCC) we
> have two loongson-2f based netbooks on which a GCC bootstrap
> and check is manageable.
> 
> Right now this farm is more oriented towards upstream userland
> developpers debug/test cycles - they get access to 12 architectures when
> they sign in. It's not really oriented towards porting
> kernel/distributions or building distribution packages which is already
> well covered by existing distribution farms and individual developpers
> and those developpers should get priority on new hardware :).
> 
> This farm project is part of the Free Software Fundation France (a
> french not-for-profit organization) effort to help free software
> development and we accept hardware and hosting donations, and also
> discounts to purchase commercial hardware when donations are not
> possible and there is significant interest in one platform.

That I think is a great solution for people who need short term access
but doesn't really solve the fundamental problem that hardware with
sufficient punch for efficient native development isn't easily available.

  Ralf

  reply	other threads:[~2009-05-19 12:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-16  3:14 Bigsur? Andrew Wiley
2009-05-18 14:13 ` Bigsur? Ralf Baechle
2009-05-18 16:13 ` Bigsur? Jon Fraser
2009-05-18 16:31   ` Bigsur? David Daney
2009-05-18 17:23     ` Bigsur? Maciej W. Rozycki
2009-05-18 17:28     ` Bigsur? Markus Gothe
2009-05-18 19:02   ` Bigsur? Imre Kaloz
2009-05-18 19:37     ` Bigsur? Jon Fraser
2009-05-18 22:23   ` Bigsur? Ralf Baechle
2009-05-18 22:47     ` Bigsur? Maciej W. Rozycki
2009-05-19 12:17       ` Bigsur? Laurent GUERBY
2009-05-19 12:53         ` Ralf Baechle [this message]
2009-05-20 18:01           ` Bigsur? Andrew Sharp
2009-05-20 19:16             ` Bigsur? Ralf Baechle
2009-05-20 19:22               ` Bigsur? Manuel Lauss
2009-05-20 20:21                 ` Bigsur? Laurent GUERBY
2009-05-20 23:17                   ` Bigsur? Ralf Baechle

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=20090519125310.GA17733@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=debio264@gmail.com \
    --cc=jfraser@broadcom.com \
    --cc=laurent@guerby.net \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.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.
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.