FS#14215 - Anjuta lacks the valgrind plugin
Attached to Project:
Arch Linux
Opened by Giuseppe Borzi (gborzi) - Monday, 13 April 2009, 14:08 GMT
Last edited by Jan de Groot (JGC) - Saturday, 02 May 2009, 18:01 GMT
Opened by Giuseppe Borzi (gborzi) - Monday, 13 April 2009, 14:08 GMT
Last edited by Jan de Groot (JGC) - Saturday, 02 May 2009, 18:01 GMT
|
Details
Description:
anjuta 2.26.0 lacks the valgrind plugin, although the packager tried to activate it with configure, valgrind is in optdepends as 'valgrind: for the valgrind debugger plugin' and is in makedepends. The problem lies in configure.in that currently has this check for activating this plugin AC_CHECK_LIB(bfd, bfd_get_error, [PLUGIN_VALGRIND_LIBS="-Wl,-Bstatic -lbfd -liberty -Wl,-Bdynamic"], valgrind="no", -liberty) this fails because libbfd requires both libiberty and *libz*.Changing the above check in configure.in to AC_CHECK_LIB(bfd, bfd_get_error, [PLUGIN_VALGRIND_LIBS="-Wl,-Bstatic -lbfd -liberty -lz -Wl,-Bdynamic"], valgrind="no", [-liberty -lz]) and regenerating configure with autoconf fixes the problem. I'm attaching the patch I used to recompile the package. On a side note, I would suggest to add ctags to optdepends, because ctags is needed by the new symbol-db plugin. anjuta complains of a missing ctags if it doesn't find it. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: Open anjuta and try to activate the valgrind plugin: it's not among the available plugins. |
This task depends upon
Closed by Jan de Groot (JGC)
Saturday, 02 May 2009, 18:01 GMT
Reason for closing: Fixed
Additional comments about closing: binutils in testing contains a correct libbfd.so, anjuta 2.26.1.0-1 is built against a fixed libbfd.so file.
Saturday, 02 May 2009, 18:01 GMT
Reason for closing: Fixed
Additional comments about closing: binutils in testing contains a correct libbfd.so, anjuta 2.26.1.0-1 is built against a fixed libbfd.so file.
Allan, would you mind building/releasing a binutils quickfix foir this? I know you have commited this already to trunk some time ago.
# Remove these symlinks, with binutils prereleases they are not ABI stable.
# Programs should compile static to the .a file.
rm -f ${startdir}/pkg/usr/lib/lib{bfd,opcodes}.so
adding a symlink in this way "cd /usr/lib && ln -s libbfd-2.19.1.20090205.so libbfd.so" fixes the missing valgrind plugin issue without the need to change configure.in and rebuild configure with autoconf. I don't think this can be considered an anjuta bug and reported upstream, anjuta's authors rely (and rightly so) on the availability of libbfd.so. Now I agree with Jan, it's a binutils bug due to the way it is packaged.
echo "INPUT (libbfd.a -liberty -lz )" >${pkgdir}/usr/lib/libbfd.so
This fixes the issue. This will be done with the gcc-4.4.0 toolchain rebuild which should be this week (provided no blocker to gcc-4.4.0 release is found).
$ echo "INPUT (libbfd.a -liberty -lz )" > /usr/lib/libbfd.so
and configure now reports it can build the valgrid plugin. Although this is a binutils bug, anjuta still needs to be rebuilt to get the plugin.