GNOME.org
 

Gtkmm-forge Digest, Vol 4, Issue 12

Send Gtkmm-forge mailing list submissions to
	gtkmm-forge lists sourceforge net

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
	gtkmm-forge-request lists sourceforge net

You can reach the person managing the list at
	gtkmm-forge-owner lists sourceforge net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gtkmm-forge digest..."


gtkmm-forge is the mailing list that receives gtkmm bug reports from bugzilla.  A daily digest is sent to gtkmm-main, to encourage people to help fixing the bugs. Do not try to unsubscribe gtkmm-forge from gtkmm-list.


Today's Topics:

   1. [Bug 352226] gtkmm-2.10.0 build problem with	gcc-3.3.6
      (gtkmm (bugzilla.gnome.org))
   2. [Bug 357830] New: broken	--enable-api-default-signal-handlers
      option (glibmm (bugzilla.gnome.org))
   3. [Bug 357830] broken	--enable-api-default-signal-handlers
      option (glibmm (bugzilla.gnome.org))
   4. [Bug 357830] broken	--enable-api-default-signal-handlers
      option (glibmm (bugzilla.gnome.org))
   5. [Bug 357830] broken	--enable-api-default-signal-handlers
      option (glibmm (bugzilla.gnome.org))


----------------------------------------------------------------------

Message: 1
Date: Mon, 25 Sep 2006 19:40:11 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 352226] gtkmm-2.10.0 build problem with
	gcc-3.3.6
To: gtkmm-forge lists sourceforge net
Message-ID: <20060925194011 BD2D76C4077 box gnome org>
Content-Type: text/plain; charset=utf-8

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=352226

gtkmm | build | Ver: 2.10.x


Joshua Moline changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jdmoline gmail com




------- Comment #6 from Joshua Moline  2006-09-25 19:39 UTC -------
Murray, as per comment #2, using "" instead of Glib::ustring() does indeed
work.  This was with gcc 3.4.6.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.



------------------------------

Message: 2
Date: Tue, 26 Sep 2006 14:35:57 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 357830] New: broken
	--enable-api-default-signal-handlers option
To: gtkmm-forge lists sourceforge net
Message-ID: <bug-357830-5595 http bugzilla gnome org/>
Content-Type: text/plain; charset=utf-8

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=357830

glibmm | build | Ver: unspecified

           Summary: broken --enable-api-default-signal-handlers option
           Product: glibmm
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: build
        AssignedTo: gtkmm-forge lists sourceforge net
        ReportedBy: jonathon jongsma gmail com
         QAContact: gtkmm-forge lists sourceforge net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


>From Matt Hoosier on the gtkmm mailing list:

The M4 macro (from scripts/reduced.m4) which controls whether default
signal handlers will be exposed as virtual functions seems to have a
typo:

AC_DEFUN([GLIBMM_ARG_ENABLE_API_DEFAULT_SIGNAL_HANDLERS],
[
 AC_ARG_ENABLE([api-exceptions],
     [  --enable-api-default-signal-handlers  Build default signal
handlers API.
                             [[default=yes]]],
     [glibmm_enable_api_default_signal_handlers="$enableval"],
     [glibmm_enable_api_default_signal_handlers='yes'])

 if test "x$glibmm_enable_api_default_signal_handlers" = "xyes"; then
 {
   AC_DEFINE([GLIBMM_DEFAULT_SIGNAL_HANDLERS_ENABLED],[1], [Defined
when the --enable-api-default-signal-handlers configure argument was
given])
 }
 fi
])

Note that the AC_ARG_ENABLE clause uses "api-exceptions" as the
salient bit, when I guess it should probably be
"api-default-signal-handlers". This has the effect that
$glibmm_enable_api_default_signal_handlers never takes on the "yes"
value, and the virtual functions are never enabled.

This seems to affect HEAD, 2-10, and 2-12 branches


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.



------------------------------

Message: 3
Date: Tue, 26 Sep 2006 14:53:23 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 357830] broken
	--enable-api-default-signal-handlers option
To: gtkmm-forge lists sourceforge net
Message-ID: <20060926145323 1BC4C6C4099 box gnome org>
Content-Type: text/plain; charset=utf-8

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=357830

glibmm | build | Ver: unspecified


Murray Cumming changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |murrayc murrayc com




------- Comment #1 from Murray Cumming  2006-09-26 14:52 UTC -------
I'm not sure how, but the configure help does list the correct option:
"
  --enable-use-deprecations
                          warn about deprecated usages [default=no]
  --enable-deprecated-api  Include (build) deprecated API in the libraries.
                              [default=yes]
  --enable-api-exceptions  Build exceptions API.
                              [default=yes]
  --enable-api-properties  Build properties API.
                              [default=yes]
  --enable-api-vfuncs  Build vfuncs API.
                              [default=yes]
  --enable-api-default-signal-handlers  Build default signal handlers API.
                              [default=yes]
"

and glibmmconfig.h does define the macro, by default:
"
#define GLIBMM_PROPERTIES_ENABLED 1
#define GLIBMM_VFUNCS_ENABLED 1
#define GLIBMM_EXCEPTIONS_ENABLED 1
#define GLIBMM_DEFAULT_SIGNAL_HANDLERS_ENABLED 1
#endif
"

But I'll fix it all the same.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.



------------------------------

Message: 4
Date: Tue, 26 Sep 2006 15:13:53 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 357830] broken
	--enable-api-default-signal-handlers option
To: gtkmm-forge lists sourceforge net
Message-ID: <20060926151353 E956D6C409D box gnome org>
Content-Type: text/plain; charset=utf-8

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=357830

glibmm | build | Ver: unspecified





------- Comment #2 from Murray Cumming  2006-09-26 15:13 UTC -------
Comitted to HEAD, glibmm-2-12, glibmm-2-10, and glibmm-2-8 branches. I don't
think new tarball releases are necessary, but tell me if I'm wrong.


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.



------------------------------

Message: 5
Date: Tue, 26 Sep 2006 15:21:23 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 357830] broken
	--enable-api-default-signal-handlers option
To: gtkmm-forge lists sourceforge net
Message-ID: <20060926152123 30EE16C4099 box gnome org>
Content-Type: text/plain; charset=utf-8

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=357830

glibmm | build | Ver: unspecified





------- Comment #3 from jonner  2006-09-26 15:20 UTC -------
You mentioned that the macro is defined by default.  One thing you might want
to check is whether it's possible to _disable_ the default signal handlers.  If
not, it might be worth re-rolling releases.  Or maybe you know the answer to
that already...


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.



------------------------------

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

------------------------------

_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest, Vol 4, Issue 12
******************************************
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]