public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Elena Zannoni <elena.zannoni@oracle.com>
Cc: frysk@sourceware.org
Subject: Re: Again the build is broken :(
Date: Fri, 24 Aug 2007 14:39:00 -0000	[thread overview]
Message-ID: <1187966328.24666.20.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <46CEEA89.7030803@oracle.com>

Hi Elena,

On Fri, 2007-08-24 at 10:26 -0400, Elena Zannoni wrote:
> This leads to the question as to what are the standard development 
> platforms for frysk.
> FC6 and FC7? Or is older stuff still used? Should there be a standard 
> platform where
> pre-commit build and tests should be performed.

I am personally using Fedora Core 6 (x86_64) as main development
platform and test everything (quickly) on Fedora 7 (x86) before
committing. But I guess other people have other platforms available. I
do appreciate the autobuilder Kris setup since that shows some more
platforms. Maybe we can change it a little to better show which patch
breaks what on which platform, but that would mean actually building
each commit, which might be a little too much for the system.

Cheers,

Mark

  reply	other threads:[~2007-08-24 14:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24  5:51 Kris Van Hees
2007-08-24  8:16 ` Mark Wielaard
2007-08-24 11:12   ` Mark Wielaard
2007-08-24 11:47     ` Mark Wielaard
2007-08-24 12:34   ` Andrew Cagney
2007-08-24 14:26     ` Elena Zannoni
2007-08-24 14:39       ` Mark Wielaard [this message]
2007-08-24 15:17         ` Phil Muldoon
2007-08-24 16:14           ` Elena Zannoni
2007-08-24 21:00             ` Andrew Cagney
2007-08-28  0:19             ` Phil Muldoon
2007-08-24 16:44         ` Kris Van Hees
2007-08-26 21:21 Kris Van Hees

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=1187966328.24666.20.camel@dijkstra.wildebeest.org \
    --to=mark@klomp.org \
    --cc=elena.zannoni@oracle.com \
    --cc=frysk@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).