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

Bug#482650: marked as done (gigedit_0.1.1-2.1(unstable/sparc/spontini): error: 'strdup' was not declared in this scope)



Your message dated Sun, 25 May 2008 11:32:03 +0000
with message-id <E1K0ESJ-0006Ax-FJ@ries.debian.org>
and subject line Bug#482650: fixed in gigedit 0.1.1-2.2
has caused the Debian Bug report #482650,
regarding gigedit_0.1.1-2.1(unstable/sparc/spontini): error: 'strdup' was not declared in this scope
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.)


-- 
482650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482650
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: gigedit
Version: 0.1.1-2.1
Severity: serious

Heya,

Building your package failed on my buildd.

| Automatic build of gigedit_0.1.1-2.1 on spontini by sbuild/sparc 99.99
| Build started at 20080524-0629
| ******************************************************************************

[...]

|  sparc-linux-gnu-g++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pthread -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-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/freetype2 -I/usr/include/libpng12 -I/usr/include/pixman-1 -I/usr/include/atk-1.0 -g -O2 -MT libgigedit_la-mainwindow.lo -MD -MP -MF .deps/libgigedit_la-mainwindow.Tpo -c mainwindow.cpp  -fPIC -DPIC -o .libs/libgigedit_la-mainwindow.o
| mainwindow.cpp: In member function 'void MainWindow::load_file(const char*)':
| mainwindow.cpp:605: error: 'strdup' was not declared in this scope
| mainwindow.cpp: In member function 'void MainWindow::on_action_add_sample()':
| mainwindow.cpp:1352: error: 'strlen' was not declared in this scope
| make[4]: *** [libgigedit_la-mainwindow.lo] Error 1
| make[4]: Leaving directory `/build/buildd/gigedit-0.1.1/src/gigedit'
| make[3]: *** [all-recursive] Error 1
| make[3]: Leaving directory `/build/buildd/gigedit-0.1.1/src'
| make[2]: *** [all-recursive] Error 1
| make[2]: Leaving directory `/build/buildd/gigedit-0.1.1'
| make[1]: *** [all] Error 2
| make[1]: Leaving directory `/build/buildd/gigedit-0.1.1'
| make: *** [build-stamp] Error 2
| dpkg-buildpackage: failure: debian/rules build gave error exit status 2
| ******************************************************************************
| Build finished at 20080524-0634
| FAILED [dpkg-buildpackage died]
| Build needed 00:01:49, 4132k disk space

A complete build log can be found at
http://buildd.debian.org/build.php?arch=sparc&pkg=gigedit&ver=0.1.1-2.1

You are missing an #include for string.h somewhere.

Marc
-- 
Fachbegriffe der Informatik - Einfach erklärt
16: SYSOP
       Vollidiot (Courtesy of Christian Weisgerber)



--- End Message ---
--- Begin Message ---
Source: gigedit
Source-Version: 0.1.1-2.2

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

gigedit_0.1.1-2.2.diff.gz
  to pool/main/g/gigedit/gigedit_0.1.1-2.2.diff.gz
gigedit_0.1.1-2.2.dsc
  to pool/main/g/gigedit/gigedit_0.1.1-2.2.dsc
gigedit_0.1.1-2.2_i386.deb
  to pool/main/g/gigedit/gigedit_0.1.1-2.2_i386.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 482650@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tobias Toedter <toddy@debian.org> (supplier of updated gigedit 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, 25 May 2008 12:41:47 +0200
Source: gigedit
Binary: gigedit
Architecture: source i386
Version: 0.1.1-2.2
Distribution: unstable
Urgency: high
Maintainer: Debian Multimedia Team <debian-multimedia@lists.debian.org>
Changed-By: Tobias Toedter <toddy@debian.org>
Description: 
 gigedit    - instrument editor for Gigasampler files
Closes: 482650
Changes: 
 gigedit (0.1.1-2.2) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Urgency set to high because of RC bug fix
   * Fix FTBFS due to missing #include statements. Thanks to Peter Green
     for the patch. Closes: #482650
Checksums-Sha1: 
 d977cc87088682687cb0691e825d8741ac73e68a 1161 gigedit_0.1.1-2.2.dsc
 a635458eed3b9d71f95cde5488b1f49db0f35396 6589 gigedit_0.1.1-2.2.diff.gz
 ba0310eaa90e57272006027cf29278155ab65d46 1003474 gigedit_0.1.1-2.2_i386.deb
Checksums-Sha256: 
 e450bbfbaf100fca464889de10046031cabd56540ab6a212e38bdc86d648fd04 1161 gigedit_0.1.1-2.2.dsc
 f6a40e30bb7c9fee16ca527e1b65b3509507516ad61ff67b714d7e676278d3ab 6589 gigedit_0.1.1-2.2.diff.gz
 359b59bbb4df5b156600b310d6c65d4b30a4bcbcb6cd1438fe3dfebbaa27e88b 1003474 gigedit_0.1.1-2.2_i386.deb
Files: 
 2ebbac4a48b630947e41aeb350a1d392 1161 sound optional gigedit_0.1.1-2.2.dsc
 a208fe72570cd3fd8c24d4c8ec9e96bf 6589 sound optional gigedit_0.1.1-2.2.diff.gz
 ecb6e3051b5cde326bb76f72d64cc148 1003474 sound optional gigedit_0.1.1-2.2_i386.deb

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

iD8DBQFIOUti3UXUABXir9YRAo+YAJoCiVV8fYeIK7RyjX1RUB3MYrtrhQCeNHyC
BX+T1en1dK/17y3C3K3TanA=
=Rq2D
-----END PGP SIGNATURE-----



--- End Message ---

Reply to: