From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Wed, 26 Mar 2014 09:50:26 -0400
To: 9fans@9fans.net
Message-ID: <e8209b75e286f46332212a000fe70a5e@brasstown.quanstro.net>
In-Reply-To: <CAA6Yd9VoqMxvUv+LEEN2f=qXMK2-iNTs+n7DebHq_Aad28gYnQ@mail.gmail.com>
References: <CAA6Yd9UXY1d_rAv+SVy-yreynCVZfuGrHCZd4h_FuwZYhAFO9w@mail.gmail.com>
	<CANUoZoH28roGrBMvsRuZ0dpfYRHUSbaFb3Nj_PbX10ws2Veb3Q@mail.gmail.com>
	<CAA6Yd9VfU3V0=QO2H29hZ9G-qnPcwqH=DSsP1yeT-WB1ky=vHw@mail.gmail.com>
	<5332c061.924ab40a.15cc.55a2@mx.google.com>
	<CAA6Yd9VoqMxvUv+LEEN2f=qXMK2-iNTs+n7DebHq_Aad28gYnQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Python/Mercurial error
Topicbox-Message-UUID: d0f54ad6-ead8-11e9-9d60-3106f5b1d025

> 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