From: steve <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ape compiler error, IND CHAR and INT
Date: Mon, 23 Jan 2012 08:13:32 +0000 [thread overview]
Message-ID: <FD238E1D-0EED-42E8-9229-ACB0170A5861@quintile.net> (raw)
In-Reply-To: <CAK8RtFokXLnNtWokmoE88KZtfc38gCupZk2sLqgUuYiq4BPd-g@mail.gmail.com>
I must have missed that one,
From your old report it seems tr problem is at line 432 of test1.bac.h
Can you reproduce the error?
-Steve
On 23 Jan 2012, at 06:47 AM, Jens Staal <staal1978@gmail.com> wrote:
> 2012/1/18 John Floren <john@jfloren.net>:
>> On Wed, Jan 18, 2012 at 10:46 AM, Martin Harriss <martin@princeton.edu> wrote:
>>> 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=0 -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
>>>> #
>>>>
>>>> The offending lines are these:
>>>>
>>>> d->d_name = strdup(name);
>>>> and
>>>> lb->lb_str = 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=1
>
> I have already added the -D_BSD_EXTENSION in the CFLAGS in the script.
next prev parent reply other threads:[~2012-01-23 8:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 18:37 John Floren
2012-01-18 18:46 ` Martin Harriss
2012-01-18 18:55 ` John Floren
2012-01-18 19:52 ` steve
2012-01-23 6:47 ` Jens Staal
2012-01-23 8:13 ` steve [this message]
2012-01-23 8:30 ` Charles Forsyth
2012-01-23 8:37 ` Jens Staal
2012-01-23 8:59 ` Charles Forsyth
[not found] ` <CAOw7k5hX5p4-9gtHhGf4Zs=kpJGLOjA9ZEbyXigC2=jBkZKnAw@mail.gmail.c>
2012-01-23 15:16 ` erik quanstrom
2012-01-24 4:43 ` Jens Staal
[not found] ` <CAK8RtFrxef6Pj149vK56Djjqd2tnh9gOXkYkYqp7LNqzSCmJ8w@mail.gmail.c>
2012-01-24 4:48 ` erik quanstrom
2012-01-24 4:48 ` erik quanstrom
[not found] <CAL4LZyjWRc0MtE5bGV35c18_JV8PjAaWUMpP1gZbdcYa26pX8A@mail.gmail.c>
2012-01-18 18:45 ` erik quanstrom
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=FD238E1D-0EED-42E8-9229-ACB0170A5861@quintile.net \
--to=steve@quintile.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).