From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <CAL4LZyj2GhGzeXjb+R+a-M_gpQAmf=dYzEJc+uO0zh0f0TsALA@mail.gmail.com>
References: <CAL4LZyjWRc0MtE5bGV35c18_JV8PjAaWUMpP1gZbdcYa26pX8A@mail.gmail.com>
	<4F171398.8020701@Princeton.EDU>
	<CAL4LZyj2GhGzeXjb+R+a-M_gpQAmf=dYzEJc+uO0zh0f0TsALA@mail.gmail.com>
From: Jens Staal <staal1978@gmail.com>
Date: Mon, 23 Jan 2012 07:47:19 +0100
Message-ID: <CAK8RtFokXLnNtWokmoE88KZtfc38gCupZk2sLqgUuYiq4BPd-g@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] ape compiler error, IND CHAR and INT
Topicbox-Message-UUID: 607d71c6-ead7-11e9-9d60-3106f5b1d025

2012/1/18 John Floren <john@jfloren.net>:
> On Wed, Jan 18, 2012 at 10:46 AM, Martin Harriss <martin@princeton.edu> w=
rote:
>> John Floren wrote:
>>>
>>> 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:
>>>
>>> cc -c -OPT:Olimit=3D0 -g -DNDEBUG -O =C2=A0-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
>>> #
>>>
>>> The offending lines are these:
>>>
>>> =C2=A0 =C2=A0d->d_name =3D strdup(name);
>>> and
>>> =C2=A0 =C2=A0lb->lb_str =3D strdup(str);
>>>
>>> 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?
>>
>>
>> No declaration in scope for the string functions, compiler thinks they
>> return INT?
>>
>> Martin
>>
>
> Yup, I r dum, needed a -D_BSD_EXTENSION in my flags to make string.h
> behave right.
>

I have a similar issue with BaCon (a ksh script converting BASIC code
to C), a modified version running under APE sh can be found here:

http://code.google.com/p/ports2plan9/source/browse/BaCon

Also this one has the problem 'incompatible types "IND CONST CHAR" and
"INT" for op "AS"'

and I have not been able to track down exactly where in the script
that the erroneous code gets generated.

issue described here:
http://code.google.com/p/ports2plan9/issues/detail?id=3D1

I have already added the -D_BSD_EXTENSION in the CFLAGS in the script.