build failure on debian

[Ritesh Raj Sarraf]

I'm trying to build appmenu and I see a build failure for a
non-existent (or Ubuntu only) header file.

Making all in src
make[3]: Entering directory `/tmp/buildd/appmenu-gtk-0.3.0/src'
make[4]: Entering directory `/tmp/buildd/appmenu-gtk-0.3.0/src'
 CC bridge.o
In file included from bridge.c:41:0:
bridge.h:23:33: fatal error: gtk/ubuntumenuproxy.h: No such file or directory
compilation terminated.
make[4]: *** [libappmenu_la-bridge.lo] Error 1
make[4]: Leaving directory `/tmp/buildd/appmenu-gtk-0.3.0/src'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/tmp/buildd/appmenu-gtk-0.3.0/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/tmp/buildd/appmenu-gtk-0.3.0'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/buildd/appmenu-gtk-0.3.0'
dh_auto_build: make -j1 returned exit code 2
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Failed autobuilding of package

Is there a fix available for this?

[Bilal Akhtar (bilalakhtar)]

Yup, this is because GTK in Ubuntu is patched with an extra file (ubuntumenuproxy.h) which sends menus over Dbus. Since this change is ubuntu-specific and we definitely don't want it to go to Debian, this bug won't be fixed. However, in your case, you can download Ubuntu's GTK source code from the repository and then build it on Debian, and use its header files to build appmenu-gtk and that'd work.

[Ritesh Raj Sarraf (rrs)]

Why don't you want to see it definitely in debian?

We keep hearing a lot about working together, but your definitely doesn't
give that impression.
On Jan 13, 2012 6:40 AM, "Bilal Akhtar" <email address hidden> wrote:

> Yup, this is because GTK in Ubuntu is patched with an extra file
> (ubuntumenuproxy.h) which sends menus over Dbus. Since this change is
> ubuntu-specific and we definitely don't want it to go to Debian, this
> bug won't be fixed. However, in your case, you can download Ubuntu's GTK
> source code from the repository and then build it on Debian, and use its
> header files to build appmenu-gtk and that'd work.
>
> ** Changed in: appmenu-gtk
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/913057
>
> Title:
> build failure on debian
>
> Status in Application menu module for GTK+:
> Invalid
>
> Bug description:
> I'm trying to build appmenu and I see a build failure for a
> non-existent (or Ubuntu only) header file.
>
> Making all in src
> make[3]: Entering directory `/tmp/buildd/appmenu-gtk-0.3.0/src'
> make[4]: Entering directory `/tmp/buildd/appmenu-gtk-0.3.0/src'
> CC bridge.o
> In file included from bridge.c:41:0:
> bridge.h:23:33: fatal error: gtk/ubuntumenuproxy.h: No such file or
> directory
> compilation terminated.
> make[4]: *** [libappmenu_la-bridge.lo] Error 1
> make[4]: Leaving directory `/tmp/buildd/appmenu-gtk-0.3.0/src'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory `/tmp/buildd/appmenu-gtk-0.3.0/src'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/tmp/buildd/appmenu-gtk-0.3.0'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/tmp/buildd/appmenu-gtk-0.3.0'
> dh_auto_build: make -j1 returned exit code 2
> make: *** [binary] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
> status 2
> E: Failed autobuilding of package
>
>
> Is there a fix available for this?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/appmenu-gtk/+bug/913057/+subscriptions
>

[Ritesh Raj Sarraf (rrs)]

You have been able to push it for qt
Could you please do the same for gtk
On Jan 13, 2012 9:26 AM, "Ritesh Raj Sarraf" <email address hidden> wrote:

> Why don't you want to see it definitely in debian?
>
> We keep hearing a lot about working together, but your definitely doesn't
> give that impression.
> On Jan 13, 2012 6:40 AM, "Bilal Akhtar" <email address hidden> wrote:
>
>> Yup, this is because GTK in Ubuntu is patched with an extra file
>> (ubuntumenuproxy.h) which sends menus over Dbus. Since this change is
>> ubuntu-specific and we definitely don't want it to go to Debian, this
>> bug won't be fixed. However, in your case, you can download Ubuntu's GTK
>> source code from the repository and then build it on Debian, and use its
>> header files to build appmenu-gtk and that'd work.
>>
>> ** Changed in: appmenu-gtk
>> Status: New => Invalid
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/913057
>>
>> Title:
>> build failure on debian
>>
>> Status in Application menu module for GTK+:
>> Invalid
>>
>> Bug description:
>> I'm trying to build appmenu and I see a build failure for a
>> non-existent (or Ubuntu only) header file.
>>
>> Making all in src
>> make[3]: Entering directory `/tmp/buildd/appmenu-gtk-0.3.0/src'
>> make[4]: Entering directory `/tmp/buildd/appmenu-gtk-0.3.0/src'
>> CC bridge.o
>> In file included from bridge.c:41:0:
>> bridge.h:23:33: fatal error: gtk/ubuntumenuproxy.h: No such file or
>> directory
>> compilation terminated.
>> make[4]: *** [libappmenu_la-bridge.lo] Error 1
>> make[4]: Leaving directory `/tmp/buildd/appmenu-gtk-0.3.0/src'
>> make[3]: *** [all] Error 2
>> make[3]: Leaving directory `/tmp/buildd/appmenu-gtk-0.3.0/src'
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory `/tmp/buildd/appmenu-gtk-0.3.0'
>> make[1]: *** [all] Error 2
>> make[1]: Leaving directory `/tmp/buildd/appmenu-gtk-0.3.0'
>> dh_auto_build: make -j1 returned exit code 2
>> make: *** [binary] Error 2
>> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
>> status 2
>> E: Failed autobuilding of package
>>
>>
>> Is there a fix available for this?
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/appmenu-gtk/+bug/913057/+subscriptions
>>
>