headers
tys lefering | 18 Nov 01:53
Picon
Picon
Favicon

xgettext messages when compiling bison git repo

compiling bison from git repo (18 nov 2009) on a fresh installed
suse linux 11.2 machine gives no errors or warnings on bison
itself but few silly warnings from running xgettext:
data/glr.c:38: warning: unterminated character constant
data/glr.c:39: warning: unterminated character constant
data/yacc.c:222: warning: unterminated character constant
data/yacc.c:1626: warning: unterminated character constant

in glr.c this is line:
# If glr.cc is including this file and thus has already set b4_pure_flag,
don't

in yacc.c this is line:
b4_copyright([Implementation for Bison's Yacc-like parsers in C])[
b4_copyright([Interface for Bison's Yacc-like parsers in C])dnl

would change the lines in glr.c/yacc.c to avoid the '
to stop the warning messages of xgettext.

and some other notes from xgettext are:
/usr/bin/xgettext: warning: file `src/parse-gram.y' extension `y' is
unknown; will try C
/usr/bin/xgettext: warning: file `src/scan-code.l' extension `l' is
unknown; will try C
/usr/bin/xgettext: warning: file `src/scan-gram.l' extension `l' is
unknown; will try C

xgettext version on suse linux 11.2 is:
xgettext (GNU gettext-tools) 0.17
Copyright (C) 1995-1998, 2000-2007 Free Software Foundation, Inc.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Joel E. Denny | 25 Nov 17:40
Favicon

Re: xgettext messages when compiling bison git repo

Hi Tys,

On Wed, 18 Nov 2009, tys lefering wrote:

> compiling bison from git repo (18 nov 2009) on a fresh installed
> suse linux 11.2 machine gives no errors or warnings on bison
> itself but few silly warnings from running xgettext:
> data/glr.c:38: warning: unterminated character constant
> data/glr.c:39: warning: unterminated character constant
> data/yacc.c:222: warning: unterminated character constant
> data/yacc.c:1626: warning: unterminated character constant

I get these warnings too.  Unless they are causing real problems, I am 
content to ignore them rather than be forced to rewrite our comments.  
What we really need is an xgettext that understands m4.

> this looks to be not a problem of bison but of the valgrind as
> it is installed on suse linux, in tests/testuite.dir/001 is:

You might want to report this to the distro or the valgrind maintainers.  
I'm not sure if we can do anything about it.

> +valgrind:  Fatal error at startup: a function redirection
> +valgrind:  which is mandatory for this platform-tool combination
> +valgrind:  cannot be set up.  Details of the redirection are:
> +valgrind:
> +valgrind:  A must-be-redirected function
> +valgrind:  whose name matches the pattern:      strlen
> +valgrind:  in an object with soname matching:   ld-linux-x86-64.so.2
> +valgrind:  was not found whilst processing
(Continue reading)

Permalink | Reply | 1 comment |
headers
tys lefering | 26 Nov 00:50
Picon
Picon
Favicon

Re: xgettext messages when compiling bison git repo

hi Joel,

>> this looks to be not a problem of bison but of the valgrind as
>> it is installed on suse linux, in tests/testuite.dir/001 is:
> You might want to report this to the distro or the valgrind maintainers.
> I'm not sure if we can do anything about it.

There is issue with valgrind installation on suse linux 11.2
http://forums.opensuse.org/applications/425841-valgrind-opensuse-11-2-a.html
solution: first enable debug repo of suse linux
then install the glibc-debug package.

Tested current bison in git with 'make maintainer-check'
and all checks report "ok" with and without valgrind,
and compilation of bison itself is perfect.

Current bison development version is very excellent.

Thanks, tys lefering.
Permalink | Reply | 0 comments |
headers
Christian Fotsing | 25 Nov 11:54
Favicon

problem with union and type in file.y

Hi.
I work with Bison 2.3, and i have define my struct 
typedef
    struct RecChem {
        Instruction *Mot;
        int Nombre;
    } * Chemin;
in another file (extern.h).
In my Yacc file, i include extern.h, and declare 
%union{
    ------
    Chemin T_Chemin;
    ---------
}
When i compile, i have this error :

expected specifier-qualifier-list before ‘Chemin’

What can i do??

Sincerly..
Permalink | Reply | 0 comments |
headers
Eric Blake | 27 Nov 13:59
Gravatar

Re: Non-portable m4 check in autoconf 2.64, 2.65, HEAD


According to Harald van Dijk on 11/26/2009 11:32 AM:
> The configure script of autoconf 2.64/2.65/HEAD fails to detect a
> suitable m4 on my system.
> I have GNU M4 1.4.13. The problem is that I'm using dash for /bin/sh
> (and my dash supports LINENO so configure doesn't silently use bash
> instead), and the m4 detection doesn't work when echo \1 prints ^A.

That means bison needs to update its autoconf submodule to today, or it
will suffer from the same problem in its reuse of the broken m4.m4 test.

--
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9 <at> byu.net
Permalink | Reply | 1 comment |

Gmane