compilation fails when --with-valgrind in effect #2836
Closed
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Date: 2011-07-11 19:10:08 +0200
From: @sjoerdmullender
To: buildtools devs <>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
Last updated: 2011-09-16 15:04:29 +0200
Comment 15934
Date: 2011-07-11 19:10:08 +0200
From: @sjoerdmullender
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0
Build Identifier:
At least on Fedora 15, if you have valgrind-devel installed, compilation fails with the default configure flags. The error is:
gdk/gdk_utils.mx: In function 'GDKmmap':
gdk/gdk_utils.mx:1436:3: error: variable '_qzz_res' set but not used [-Werror=unused-but-set-variable]
gdk/gdk_utils.mx: In function 'GDKmunmap':
gdk/gdk_utils.mx:1451:2: error: variable '_qzz_res' set but not used [-Werror=unused-but-set-variable]
cc1: all warnings being treated as errors
The reason is that the VALGRIND_MALLOCLIKE_BLOCK and VALGRIND_FREELIKE_BLOCK macros contain variables that are assigned to but never otherwise used. Unfortunately this is not something we can fix in our code.
Options are: remove the valgrind-specific code (the only thing it does is provide a better stack trace); or use less strict compilation flags when compiling gdk_utils.
Reproducible: Always
Comment 15983
Date: 2011-07-25 10:59:27 +0200
From: @sjoerdmullender
Changeset 6f076133eeb0 made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6f076133eeb0
Changeset description:
Comment 16018
Date: 2011-07-29 10:58:18 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
Comment 16053
Date: 2011-07-29 13:22:59 +0200
From: @sjoerdmullender
This has been "fixed" in the sense that by default valgrind support is not enabled anymore. If you want valgrind support, you have to enable it, and you have to disable "strict" compilation.
Comment 16230
Date: 2011-09-16 15:04:29 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
The text was updated successfully, but these errors were encountered: