Bug 394925 – compilation program with x11-libs/gtksourceview:2 fails if G_DISABLE_DEPRECATED is defined

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Sergey Ilinykh 2011-12-16 12:19:21 UTC]

this happens because gtksourcestylescheme.h knows nothing about G_CONST_RETURN
when G_DISABLE_DEPRECATED is defined.
so this header must be patched.

Reproducible: Always

[Comment 1 Alexandre Rostovtsev (RETIRED) 2011-12-16 17:48:54 UTC]

Are there any ebuilds in portage that fail as a result of G_CONST_RETURN in gtksourceview:2 headers, or does this only affect users who are doing their own software development?

[Comment 2 Sergey Ilinykh 2011-12-16 20:01:49 UTC]

I dunno. I tried to compile my own

[Comment 3 Sergey Ilinykh 2011-12-16 20:04:03 UTC]

if more exactly its not mine. its gmanedit from my overlay

[Comment 4 Alexandre Rostovtsev (RETIRED) 2011-12-17 01:59:29 UTC]

The reason for my question is that ebuilds in portage should not be building with -DG_DISABLE_DEPRECATED. It is a useful tool for upstream developers of a package to make sure that they are using the latest glib API, but for average end users it only causes mysterious build failures after glib updates.

Fixed in 2.10.5-r2.

>*gtksourceview-2.10.5-r2 (17 Dec 2011)
> 
>  17 Dec 2011; Alexandre Rostovtsev <[e-mail]>
>  +gtksourceview-2.10.5-r2.ebuild,
>  +files/gtksourceview-2.10.5-G_CONST_RETURN.patch:
>  Add patch from gtksourceview-3.x to not use G_CONST_RETURN in public headers
>  (bug #394925, thanks to Rion for reporting).

[Comment 5 Sergey Ilinykh 2011-12-17 07:04:44 UTC]

thanks for notice. I'll consider it next time

[Comment 6 Pacho Ramos 2011-12-17 09:49:21 UTC]

(In reply to comment #3)
> if more exactly its not mine. its gmanedit from my overlay

Also would be interesting to let gmanedit developers they shouldn't release stable tarballs with *DISABLE_DEPRECATED* flags used by default, they are oriented to development purposes ;)