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

Bug#527667: marked as done (sineshaper: FTBFS: dssiuiclient.hpp:102: error: ISO C++ forbids declaration of 'signal' with no type)



Your message dated Sun, 16 Aug 2009 22:11:17 +0000
with message-id <E1Mcnwb-0006Hh-VY@ries.debian.org>
and subject line Bug#527667: fixed in sineshaper 0.4.2-4.1
has caused the Debian Bug report #527667,
regarding sineshaper: FTBFS: dssiuiclient.hpp:102: error: ISO C++ forbids declaration of 'signal' with no type
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 owner@bugs.debian.org
immediately.)


-- 
527667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527667
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sineshaper
Version: 0.4.2-4
Severity: serious
User: debian-qa@lists.debian.org
Usertags: qa-ftbfs-20090508 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  x86_64-linux-gnu-g++ -DPACKAGE_NAME=\"sineshaper\" -DPACKAGE_TARNAME=\"sineshaper\" -DPACKAGE_VERSION=\"0.4.2\" "-DPACKAGE_STRING=\"sineshaper 0.4.2\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"sineshaper\" -DVERSION=\"0.4.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DSTDC_HEADERS=1 -DHAVE_FCNTL_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_UNISTD_H=1 -DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 -DHAVE_MEMSET=1 -DHAVE_STRDUP=1 -I. -I. -D_REENTRANT -pthread -I/usr/include/libglademm-2.4 -I/usr/lib/libglademm-2.4/include -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/libglade-2.0 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/giomm-2.4 -I/usr/lib/giomm-2.4/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/include/atkmm-1.6 -I/usr/include/gtk-2.0 -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/cairomm-1.0 -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/directfb -I/usr/include/libpng12 -I/usr/include/atk-1.0 -I/usr/include/libxml2 -D_XOPEN_SOURCE -O3 -fomit-frame-pointer -fstrength-reduce -funroll-loops -ffast-math -DNDEBUG -Wall -ansi -pedantic -MT dssiuiclient.lo -MD -MP -MF .deps/dssiuiclient.Tpo -c dssiuiclient.cpp  -fPIC -DPIC -o .libs/dssiuiclient.o
> In file included from dssiuiclient.cpp:34:
> dssiuiclient.hpp:102: error: ISO C++ forbids declaration of 'signal' with no type
> dssiuiclient.hpp:102: error: expected ';' before '<' token
> dssiuiclient.hpp:105: error: ISO C++ forbids declaration of 'signal' with no type
> dssiuiclient.hpp:105: error: expected ';' before '<' token
> dssiuiclient.hpp:108: error: ISO C++ forbids declaration of 'signal' with no type
> dssiuiclient.hpp:108: error: expected ';' before '<' token
> dssiuiclient.hpp:137: error: ISO C++ forbids declaration of 'signal' with no type
> dssiuiclient.hpp:137: error: expected ';' before '<' token
> dssiuiclient.hpp: In member function 'void DSSIUIClient::control_receiver()':
> dssiuiclient.hpp:178: error: 'control_received' was not declared in this scope
> dssiuiclient.hpp: In member function 'void DSSIUIClient::program_receiver()':
> dssiuiclient.hpp:191: error: 'program_received' was not declared in this scope
> dssiuiclient.hpp: In member function 'void DSSIUIClient::configure_receiver()':
> dssiuiclient.hpp:200: error: 'configure_received' was not declared in this scope
> dssiuiclient.cpp: In constructor 'DSSIUIClient::DSSIUIClient(int, char**, bool)':
> dssiuiclient.cpp:68: error: 'control_received' was not declared in this scope
> dssiuiclient.cpp: In member function 'void DSSIUIClient::send_program(int, int)':
> dssiuiclient.cpp:163: error: 'program_received' was not declared in this scope
> dssiuiclient.cpp: In member function 'bool DSSIUIClient::check_shared_memory()':
> dssiuiclient.cpp:290: error: 'plugin_attached' was not declared in this scope
> make[3]: *** [dssiuiclient.lo] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2009/05/08/sineshaper_0.4.2-4_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |



--- End Message ---
--- Begin Message ---
Source: sineshaper
Source-Version: 0.4.2-4.1

We believe that the bug you reported is fixed in the latest version of
sineshaper, which is due to be installed in the Debian FTP archive:

sineshaper_0.4.2-4.1.diff.gz
  to pool/main/s/sineshaper/sineshaper_0.4.2-4.1.diff.gz
sineshaper_0.4.2-4.1.dsc
  to pool/main/s/sineshaper/sineshaper_0.4.2-4.1.dsc
sineshaper_0.4.2-4.1_amd64.deb
  to pool/main/s/sineshaper/sineshaper_0.4.2-4.1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 527667@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb <lamby@debian.org> (supplier of updated sineshaper package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 16 Aug 2009 21:26:50 +0100
Source: sineshaper
Binary: sineshaper
Architecture: source amd64
Version: 0.4.2-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Team <debian-multimedia@lists.debian.org>
Changed-By: Chris Lamb <lamby@debian.org>
Description: 
 sineshaper - Monophonic synth plugin with two oscillators and waveshapers
Closes: 527667
Changes: 
 sineshaper (0.4.2-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Specify sigc:: namespace to avoid conflicts with signal(2).
     (Closes: #527667)
Checksums-Sha1: 
 a9c5961271e7df336b8c838848cce26b15b18a4c 1299 sineshaper_0.4.2-4.1.dsc
 2ddd21cdbc83e917cb8ec1791153d71b0e0eb5c5 520175 sineshaper_0.4.2.orig.tar.gz
 a6e2c4e16e48cd8a785e5001ffed51556e99abfa 12893 sineshaper_0.4.2-4.1.diff.gz
 9c8474cf9003be08e4d5f82143203b5eca2b2e13 305906 sineshaper_0.4.2-4.1_amd64.deb
Checksums-Sha256: 
 a2c2ba37407a9cd04ebd4b25ddf0061cb02097917130ad1c6607a0cc02a913e8 1299 sineshaper_0.4.2-4.1.dsc
 2a08f6049c29cf71d167e8615b2fe25748406fc0f7d3a76e50f4672602104867 520175 sineshaper_0.4.2.orig.tar.gz
 df47df96af8c7436e5af73fcdfeafbf7378d631ca556d3f00a1551010b77e948 12893 sineshaper_0.4.2-4.1.diff.gz
 096269f64846126fabdd7f51deb5f9e96a655b48ebdeca823783f97b6766540b 305906 sineshaper_0.4.2-4.1_amd64.deb
Files: 
 431f32dc83b92a4a4d66297655e2cbe5 1299 sound optional sineshaper_0.4.2-4.1.dsc
 952cb5bde0ae4fe2274859df5ed1ee61 520175 sound optional sineshaper_0.4.2.orig.tar.gz
 6d08fb66d1dee4d312d7632c39380811 12893 sound optional sineshaper_0.4.2-4.1.diff.gz
 caf77fd123efee1bfbcd39f1e9bcb8cf 305906 sound optional sineshaper_0.4.2-4.1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqIcHAACgkQ5/8uW2NPmiAADgCfXBM7vgqWkRqpQXPObPCGwWpf
aWwAniOqZ+JmxtbfRyUN3AIha/VdrWDo
=Xs0s
-----END PGP SIGNATURE-----



--- End Message ---

Reply to: