Re: xgettext messages when compiling bison git repo

[Joel E. Denny]

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
> +valgrind:  symbols from the object with soname: ld-linux-x86-64.so.2
> +valgrind:
> +valgrind:  Possible fixes: (1, short term): install glibc's debuginfo
> +valgrind:  package on this machine.  (2, longer term): ask the packagers
> +valgrind:  for your Linux distribution to please in future ship a non-
> +valgrind:  stripped ld.so (or whatever the dynamic linker .so is called)
> +valgrind:  that exports the above-named function using the standard
> +valgrind:  calling conventions for this platform.
> +valgrind:
> +valgrind:  Cannot continue -- exiting now.  Sorry.

To see if this is specific to bison, you might try compiling some other C 
program that uses strlen and then run it with valgrind.  Regardless of the 
result, you'll probably want to try the suggestions in the valgrind error 
message.  If you find out that something in bison needs to change, please 
let us know.

Thanks.