From: Petr Machata <pmachata@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Carlos Eduardo Seo <cseo@linux.vnet.ibm.com>,
Frysk Mailing List <frysk@sourceware.org>
Subject: Re: Frysk for ppc broken?
Date: Thu, 27 Mar 2008 12:21:00 -0000 [thread overview]
Message-ID: <20080327121557.GB32749@hridell.englab.brq.redhat.com> (raw)
In-Reply-To: <1206613434.3374.4.camel@dijkstra.wildebeest.org>
[-- Attachment #1: Type: text/plain, Size: 333 bytes --]
On Thu, Mar 27, 2008 at 11:23:54AM +0100, Mark Wielaard wrote:
> If it doesn't then you would get the error you are seeing. I don't know
> why that would happen though.
Error similar to this one used to happen for me routinely when I did a
rebuild after rebase without first wiping the build directory. Could
that be the case?
PM
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-03-27 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 1:10 Carlos Eduardo Seo
2008-03-27 10:24 ` Mark Wielaard
2008-03-27 12:21 ` Petr Machata [this message]
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=20080327121557.GB32749@hridell.englab.brq.redhat.com \
--to=pmachata@redhat.com \
--cc=cseo@linux.vnet.ibm.com \
--cc=frysk@sourceware.org \
--cc=mark@klomp.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).