From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Python/Mercurial error
Date: Wed, 26 Mar 2014 09:50:26 -0400 [thread overview]
Message-ID: <e8209b75e286f46332212a000fe70a5e@brasstown.quanstro.net> (raw)
In-Reply-To: <CAA6Yd9VoqMxvUv+LEEN2f=qXMK2-iNTs+n7DebHq_Aad28gYnQ@mail.gmail.com>
> Yes, you are right. I see an empty enum declaration:
>
> enum {
> }
>
> .. in between the "extern .. tokenize.." and "extern .. malloc .. "
> declarations.
>
> I will see how this file is generated. Thank you very much. I am
> running 9atom and not the Bell Labs plan9. I am not sure if some
> structures are not in sync in any header files.
i've seen this before. but i don't exactly remember how i cleared
it up. i think it involved mk'ing smaller bits, like mk stage first.
i didn't see this error the last time i tried.
- erik
next prev parent reply other threads:[~2014-03-26 13:50 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 3:59 Ramakrishnan Muthukrishnan
2014-03-26 7:35 ` David du Colombier
2014-03-26 11:09 ` Ramakrishnan Muthukrishnan
2014-03-26 11:53 ` peterhull90
2014-03-26 12:08 ` Ramakrishnan Muthukrishnan
2014-03-26 13:50 ` erik quanstrom [this message]
2014-04-02 5:19 ` David du Colombier
2014-04-02 5:40 ` David du Colombier
2014-04-02 7:29 ` kokamoto
2014-04-03 5:12 ` kokamoto
2014-04-03 6:00 ` David du Colombier
2014-04-03 6:04 ` erik quanstrom
2014-04-02 12:48 ` erik quanstrom
2014-04-03 5:50 ` David du Colombier
2014-04-03 5:58 ` erik quanstrom
2014-04-03 6:15 ` Jeff Sickel
2014-04-03 6:20 ` David du Colombier
2014-04-03 6:24 ` erik quanstrom
2014-04-03 17:18 ` Ramakrishnan Muthukrishnan
2014-04-03 17:21 ` erik quanstrom
2014-04-03 17:57 ` David du Colombier
2014-04-03 18:01 ` erik quanstrom
2014-04-03 18:23 ` David du Colombier
2014-04-04 1:09 ` Ramakrishnan Muthukrishnan
2014-04-04 1:15 ` erik quanstrom
2014-04-03 18:04 ` Ramakrishnan Muthukrishnan
2014-04-03 19:21 ` David du Colombier
2014-04-04 5:39 ` Jeff Sickel
2014-04-07 18:27 ` Ramakrishnan Muthukrishnan
2014-04-04 10:53 ` Ramakrishnan Muthukrishnan
2014-04-04 11:38 ` David du Colombier
2014-03-26 12:09 ` Mark van Atten
2014-03-26 12:38 ` David du Colombier
2014-03-26 13:23 ` Ramakrishnan Muthukrishnan
2014-03-31 5:44 ` kokamoto
2014-03-31 6:23 ` David du Colombier
2014-03-31 6:47 ` kokamoto
2014-03-31 13:00 ` erik quanstrom
2014-04-01 0:57 ` kokamoto
2014-04-01 1:03 ` erik quanstrom
2014-04-01 2:27 ` kokamoto
2014-04-01 3:05 ` erik quanstrom
2014-04-01 6:46 ` kokamoto
2014-04-01 13:54 ` erik quanstrom
2014-04-02 2:54 ` kokamoto
2014-04-02 5:10 ` David du Colombier
2014-04-02 6:20 ` kokamoto
2014-03-26 13:47 ` erik quanstrom
2014-03-26 14:13 ` David du Colombier
2014-03-26 14:19 ` Ramakrishnan Muthukrishnan
2014-03-26 13:24 ` Ramakrishnan Muthukrishnan
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=e8209b75e286f46332212a000fe70a5e@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).