[Top][All Lists]

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

xgettext messages when compiling bison git repo

From: tys lefering
Subject: xgettext messages when compiling bison git repo
Date: Wed, 18 Nov 2009 01:53:03 +0100
User-agent: SquirrelMail/1.4.18

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,

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.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Ulrich Drepper.

when running "make maintainer-check" all tests are oke but when the
tests using valgrind are run then all checks are marked as failed.
valgrind is installed on my machine and config.log reports it is
found. the version on suse linux 11.2 is: valgrind-3.5.0

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:

#                             -*- compilation -*-
1. input.at:27: testing ...
./input.at:35: VALGRIND_OPTS="$VALGRIND_OPTS --leak-check=summary
--show-reachable=no"; export VALGRIND_OPTS; bison input.y
--- -   2009-11-18 01:29:10.020705015 +0100
01:29:10.000000000 +0100
@@ -1,3 +1,21 @@
-input.y:2.13-14: integer out of range: `$1'
-input.y:3.13-14: integer out of range: address@hidden'
+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:  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:  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:  Cannot continue -- exiting now.  Sorry.

1. input.at:27: 1. Invalid $n and @n (input.at:27): FAILED (input.at:35)

attached the compilation log and the maintainer-check log.

thanks, tys lefering.

Attachment: checklog.txt.gz
Description: GNU Zip compressed data

Attachment: compilelog.txt.gz
Description: GNU Zip compressed data

reply via email to

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