From mboxrd@z Thu Jan  1 00:00:00 1970
References: <CAL4LZyjWRc0MtE5bGV35c18_JV8PjAaWUMpP1gZbdcYa26pX8A@mail.gmail.com>
	<4F171398.8020701@Princeton.EDU>
	<CAL4LZyj2GhGzeXjb+R+a-M_gpQAmf=dYzEJc+uO0zh0f0TsALA@mail.gmail.com>
From: steve <steve@quintile.net>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <CAL4LZyj2GhGzeXjb+R+a-M_gpQAmf=dYzEJc+uO0zh0f0TsALA@mail.gmail.com>
Message-Id: <BAC49C58-C529-425C-A646-599AE82EB56E@quintile.net>
Date: Wed, 18 Jan 2012 19:52:39 +0000
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: [9fans] ape compiler error, IND CHAR and INT
Topicbox-Message-UUID: 5e994ede-ead7-11e9-9d60-3106f5b1d025

I think you want=20

Sent from my iPad

On 18 Jan 2012, at 06:55 PM, John Floren <john@jfloren.net> wrote:

> On Wed, Jan 18, 2012 at 10:46 AM, Martin Harriss <martin@princeton.edu> wr=
ote:
>> John Floren wrote:
>>>=20
>>> I figured I'd try building Python from the source on their website
>>> just for kicks. Configure went ok, but when I went to run "make", it
>>> soon bailed out with this error:
>>>=20
>>> cc -c -OPT:Olimit=3D0 -g -DNDEBUG -O  -I. -IInclude -I./Include
>>> -DPy_BUILD_CORE -o Parser/grammar.o Parser/grammar.c
>>> cc: flag -P ignored
>>> cc: flag -: ignored
>>> cc: can't find library for -l
>>> /usr/john/Python-2.7.2/Parser/grammar.c:46[stdin:12906] incompatible
>>> types: "IND CHAR" and "INT" for op "AS"
>>> /usr/john/Python-2.7.2/Parser/grammar.c:108[stdin:12968] incompatible
>>> types: "IND CHAR" and "INT" for op "AS"
>>> cc: cpp: 8c 896765: error
>>> *** Error code 1
>>> #
>>>=20
>>> The offending lines are these:
>>>=20
>>>    d->d_name =3D strdup(name);
>>> and
>>>    lb->lb_str =3D strdup(str);
>>>=20
>>> d_name and lb_str are both defined as char*, and strdup is supposed to
>>> return a char*. However, if I'm reading that error message correctly,
>>> it thinks strdup is trying to return a char*. Does anyone recognize
>>> what's going on?
>>=20
>>=20
>> No declaration in scope for the string functions, compiler thinks they
>> return INT?
>>=20
>> Martin
>>=20
>=20
> Yup, I r dum, needed a -D_BSD_EXTENSION in my flags to make string.h
> behave right.