bug-bison
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building bison from master fails: "conflicting types for 'code_get_l


From: Stefano Lattarini
Subject: Re: Building bison from master fails: "conflicting types for 'code_get_leng'"
Date: Mon, 14 May 2012 23:11:50 +0200

On 05/14/2012 02:01 PM, Akim Demaille wrote:
> 
> Le 13 mai 2012 à 12:46, Stefano Lattarini a écrit :
> 
>> When I try to bootstrap and build bison from latest master on my Debian
>> system, I see this failure:
>>
>>  ...
>>  CC       src/src_bison-reduce.o
>>  CC       src/src_bison-relation.o
>>  CC       src/src_bison-scan-code-c.o
>> In file included from src/scan-code-c.c:3:0:
>> src/scan-code.c:789:11: error: conflicting types for 'code_get_leng'
>> ./src/flex-scanner.h:28:1: note: previous declaration of 'code_get_leng' was 
>> here
>> In file included from src/scan-code-c.c:3:0:
>> src/scan-code.c:2344:11: error: conflicting types for 'code_get_leng'
>> ./src/flex-scanner.h:28:1: note: previous declaration of 'code_get_leng' was 
>> here
>> Makefile:3833: recipe for target 'src/src_bison-scan-code-c.o' failed
>> make[2]: *** [src/src_bison-scan-code-c.o] Error 1
>>
>> Attached is the config.log.  I'm using Automake and Autoconf from master, and
>> flex 2.5.36.  Let me know if you need more information.
> 
> Hi Stefano,
> 
> Thanks for the report.  As far as I know there is no such things
> as Flex 2.5.36.  Where does it come from?
>
Basically, it was a version of flex built from its development branch.
But the error persists also with flex 2.5.35 (installed from a Debian
package).

> Could you provide me with the conflicted types?
> 

>From 'src/scan-code.c':

    220:typedef size_t yy_size_t;
    ...
    679:#define FLEX_PREFIX(Id) code_ ## Id
    680:#include <src/flex-scanner.h>
    ...
    789:yy_size_t code_get_leng (void );

>From 'src/flex-scanner.h':

    28:int   FLEX_PREFIX (get_leng) (void);

HTH,
  Stefano



reply via email to

[Prev in Thread] Current Thread [Next in Thread]