9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <john@jfloren.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: Wed, 18 Jan 2012 10:55:33 -0800	[thread overview]
Message-ID: <CAL4LZyj2GhGzeXjb+R+a-M_gpQAmf=dYzEJc+uO0zh0f0TsALA@mail.gmail.com> (raw)
In-Reply-To: <4F171398.8020701@Princeton.EDU>

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.



  reply	other threads:[~2012-01-18 18:55 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 [this message]
2012-01-18 19:52     ` steve
2012-01-23  6:47     ` Jens Staal
2012-01-23  8:13       ` steve
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='CAL4LZyj2GhGzeXjb+R+a-M_gpQAmf=dYzEJc+uO0zh0f0TsALA@mail.gmail.com' \
    --to=john@jfloren.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).