Your message dated Thu, 18 Aug 2016 21:48:45 +0200 with message-id <5940918.oXvqdSURKC@pendragon> and subject line Fixed in 0.8.12-1 has caused the Debian Bug report #749194, regarding Conflicting return types of function mm_support to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 749194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: kwave Version: 0.8.11-1-1 Severity: minor Usertags: goto-cc Tags: upstream Forwarded: https://sourceforge.net/p/kwave/bugs/39/ During a rebuild of all Debian packages in a clean sid chroot (and cowbuilder+pbuilder) the build failed with the following error. Please note that we use our research compiler tool-chain (using tools from the cbmc package), which permits extended reporting on type inconsistencies at link time. [...] Linking CXX shared library libkwave.so error: conflicting function declarations "mm_support" old definition in module cputest file /srv/jenkins-slave/workspace/sid-goto-cc-kwave/kwave-0.8.11-1/libkwave/cputest.c line 62 unsigned int (void) new definition in module memcpy file /srv/jenkins-slave/workspace/sid-goto-cc-kwave/kwave-0.8.11-1/libkwave/memcpy.c line 69 signed int (void) libkwave/CMakeFiles/libkwave.dir/build.make:2370: recipe for target 'libkwave/libkwave.so.0.8.11' failed make: *** [libkwave/libkwave.so.0.8.11] Error 1 make: Leaving directory '/srv/jenkins-slave/workspace/sid-goto-cc-kwave/kwave-0.8.11-1/obj-x86_64-linux-gnu' CMakeFiles/Makefile2:376: recipe for target 'libkwave/CMakeFiles/libkwave.dir/all' failed make: *** [libkwave/CMakeFiles/libkwave.dir/all] Error 2 It seems both the forward declaration in memcpy.c as well as the declaration of rval here http://sources.debian.net/src/kwave/0.8.11-1-1/libkwave/cputest.c?hl=64#L62 should be fixed to be unsigned. This will ensure that future CPU ids do not introduce undefined behaviour (at present, the code should work ok as only a small number of bits is used). Best, Michael
Description: PGP signature
--- End Message ---
--- Begin Message ---Source: kwave Source-Version: 0.8.12-1-1 Hi, this issues was fixed upstream in kwave 0.8.12, released upstream as 0.8.12-1, and 0.8.12-1-1 as first upload in Debian. Thanks, -- Pino Toscano
Description: This is a digitally signed message part.
--- End Message ---
_______________________________________________ pkg-kde-extras mailing list firstname.lastname@example.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-extras