From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <5332c061.924ab40a.15cc.55a2@mx.google.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>
From: Ramakrishnan Muthukrishnan <vu3rdd@gmail.com>
Date: Wed, 26 Mar 2014 17:38:21 +0530
Message-ID: <CAA6Yd9VoqMxvUv+LEEN2f=qXMK2-iNTs+n7DebHq_Aad28gYnQ@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] Python/Mercurial error
Topicbox-Message-UUID: d0d452ea-ead8-11e9-9d60-3106f5b1d025

On Wed, Mar 26, 2014 at 5:23 PM,  <peterhull90@gmail.com> wrote:
> Could you post or have a look at libc_plan9.h - that file is generated by
> stripping out some things from /sys/include/libc.h and it appears that
> something in that process has generated a syntax error.

Pete,

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.

> ps. I think it=E2=80=99s impossible to copy from vbox unless you have gue=
st
> additions installed and AFAIK guest additions for plan9 have not been
> written.

Ah, okay. Thanks. I think I will install it on natively on my desktop
PC this weekend.

Thanks again.
Ramakrishnan