erreur: extra ';' in glibmm2.4 drive.h

Bug #338364 reported by Guillaume Hain
2
Affects Status Importance Assigned to Milestone
glibmm2.4 (Ubuntu)
Fix Released
Undecided
Didier Roche-Tolomelli

Bug Description

Description: Ubuntu jaunty (development branch)
Release: 9.04

libgtkmm-2.4-dev:
  Installed : 1:2.15.3-0ubuntu2
  Candidate : 1:2.15.3-0ubuntu2
 Table version :
 *** 1:2.15.3-0ubuntu2 0
        500 http://fr.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

When compiling an application using gtkmm, the build fails with the following errors:

In file included from /usr/include/giomm-2.4/giomm.h:30,
                 from /usr/include/gtkmm-2.4/gtkmm.h:30,
                 from trackertool.h:29,
                 from trackertool.cpp:24:
/usr/include/giomm-2.4/giomm/drive.h:270: erreur: extra ‘;’
/usr/include/giomm-2.4/giomm/drive.h:278: erreur: extra ‘;’
/usr/include/giomm-2.4/giomm/drive.h:286: erreur: extra ‘;’

Related branches

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

The file is in libglibmm-2.4-dev, not gtkmm.2.4: reassigning
.
$ apt-file search /usr/include/giomm-2.4/giomm/drive.h
libglibmm-2.4-dev: /usr/include/giomm-2.4/giomm/drive.h

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Ok, I can confirm the bug.

Hum, you are compiling with -pedantic option, isn't it? ;)
I will patch the file and send to upstream.

More materials for the exact reason:
http://gcc.gnu.org/ml/gcc-help/2008-01/msg00221.html

Changed in glibmm2.4:
status: New → Triaged
assignee: nobody → didrocks
status: Triaged → In Progress
Revision history for this message
Murray Cumming (murrayc) wrote :

This is already fixed in svn and will be in the next glibmm tarball release.

However, tarball builds of applications should never use -Werror.

Changed in glibmm2.4:
status: In Progress → Fix Committed
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

@Murray Cumming : ok, no need to forward upstream so. Thanks!
I just patch 2.19.8 which I am updating in case we haven't the time to have a new one for jaunty.

Changed in glibmm2.4:
status: Fix Committed → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package glibmm2.4 - 2.19.8-0ubuntu1

---------------
glibmm2.4 (2.19.8-0ubuntu1) jaunty; urgency=low

  * New upstream release (LP: #338481)
    - Added FILE_CREATE_REPLACE_DESTINATION enum value.
    - Added Error::TOO_MANY_OPEN_FILES error code.
    - Fix some compiler warnings about extra ;s. (LP: #338364)
  * bump SHVER in debian/rules

 -- Didier Roche <email address hidden> Thu, 05 Mar 2009 23:03:11 +0100

Changed in glibmm2.4:
status: Triaged → Fix Released
Revision history for this message
Guillaume Hain (zedtux) wrote :

Thanks for the quick help !! :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.