From: David F Barrera <dfbp@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: PAE Build Break
Date: Tue, 08 Nov 2005 10:23:30 -0600 [thread overview]
Message-ID: <4370D102.3050705@us.ibm.com> (raw)
In-Reply-To: <99ddf8a1437f69038a16aac199cd40f3@cl.cam.ac.uk>
Keir Fraser wrote:
>
> On 8 Nov 2005, at 16:06, David F Barrera wrote:
>
>> Bugzilla Bug 389 - PAE build break- mm.c:3250: error: parse error
>> before numeric constant
>> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=389
>
>
> I think maybe your tree is corrupted. PAE builds fine for me and the
> compile error makes no sense when I look at the code.
You are correct. Even though the tree correctly showed the last
changeset on the history, it was corrupt. Also, the update (hg pull -u)
had gone smoothly, so I did not suspect the tree being corrupt.
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
prev parent reply other threads:[~2005-11-08 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 16:06 PAE Build Break David F Barrera
2005-11-08 16:21 ` Keir Fraser
2005-11-08 16:23 ` David F Barrera [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=4370D102.3050705@us.ibm.com \
--to=dfbp@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.