Summary: | media-libs/babl-0.1.(8|10) fails to compile with USE="introspection" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mike Auty (RETIRED) <ikelos> |
Component: | Current packages | Assignee: | Sebastian Pipping <sping> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | 4nykey, aklhfex, atoth, bambucha14, benjamin1506, brad, dabbott, darkcircle.0426, eric.chatellier, gentoo-bugs, gentoo.guillaume, gentoo.org, gentoo, jason, johannis.gdev, keenblade, marduk, msporysz06, rh1, yamadharma |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 416587 | ||
Attachments: |
babl-0.1.10 build.log
patch to fix gir generation from OpenSuse package[1] babl-0.1.10 build log after applying upstream patch from comment #3 ebuild with opensuse patch failed patch log using new ebuild and patch babl-0.1.10-gir-build-fix.patch babl-0.1.10-r1.ebuild |
Description
Mike Auty (RETIRED)
2012-04-26 18:57:04 UTC
Sorry, forgot to assign to the maintainer... I'm hitting the exact same problem on ~x86 as well. Any solutions yet? It seems to be a problem with the g-i-r-scanner? Possible fix from upstream: http://git.gnome.org/browse/babl/commit/?id=c024c89f95de4a8fa95ba96790dac61768d11a17 i have same problem on @amd64
and it cause also block other package from install:
>>> Verifying ebuild manifests
>>> Running pre-merge checks for dev-libs/boost-1.49.0-r1
>>> Running pre-merge checks for www-plugins/adobe-flash-11.2.202.235
>>> Starting parallel fetch
>>> Emerging (1 of 24) media-libs/babl-0.1.10
>>> Failed to emerge media-libs/babl-0.1.10, Log file:
>>> '/var/log/portage/media-libs:babl-0.1.10:20120509-131349.log'
*** Resuming merge...
* emerge --keep-going: www-plugins/adobe-flash-11.2.202.235 dropped due to
* unsatisfied dependency.
* emerge --keep-going: gnome-extra/yelp-3.4.1 dropped due to unsatisfied
* dependency.
* emerge --keep-going: x11-wm/openbox-3.5.0_p20111019 dropped due to
* unsatisfied dependency.
* emerge --keep-going: dev-util/glade-3.12.1 dropped due to unsatisfied
* dependency.
* emerge --keep-going: media-sound/mpg123-1.14.1 dropped due to unsatisfied
* dependency.
* emerge --keep-going: gnome-base/libgnome-keyring-3.2.2 dropped due to
* unsatisfied dependency.
* emerge --keep-going: media-libs/taglib-1.7.2 dropped due to unsatisfied
* dependency.
* emerge --keep-going: dev-python/reportlab-2.5-r1 dropped due to unsatisfied
* dependency.
* emerge --keep-going: dev-libs/boost-1.49.0-r1 dropped due to unsatisfied
* dependency.
* emerge --keep-going: app-admin/conky-1.9.0 dropped due to unsatisfied
* dependency.
* emerge --keep-going: x11-misc/shutter-0.88.3 dropped due to unsatisfied
* dependency.
* emerge --keep-going: dev-lang/php-5.4.3 dropped due to unsatisfied
* dependency.
* emerge --keep-going: dev-java/jdbc-postgresql-9.1_p902 dropped due to
* unsatisfied dependency.
* emerge --keep-going: gnome-base/gnome-keyring-3.2.2 dropped due to
* unsatisfied dependency.
* emerge --keep-going: media-video/mplayer2-9999 dropped due to unsatisfied
* dependency.
* emerge --keep-going: dev-vcs/mercurial-2.2.1 dropped due to unsatisfied
* dependency.
* emerge --keep-going: app-portage/eix-0.25.4 dropped due to unsatisfied
* dependency.
* emerge --keep-going: dev-java/jruby-1.6.7.2 dropped due to unsatisfied
* dependency.
* emerge --keep-going: media-gfx/gimp-2.8.0 dropped due to unsatisfied
* dependency.
* emerge --keep-going: media-libs/gegl-0.2.0 dropped due to unsatisfied
* dependency.
* emerge --keep-going: dev-java/itext-2.1.5-r1 dropped due to unsatisfied
* dependency.
* emerge --keep-going: sci-geosciences/googleearth-6.2.2.6613 dropped due to
* unsatisfied dependency.
* emerge --keep-going: app-office/scribus-1.4.1 dropped due to unsatisfied
* dependency.
Possible workaround (worked for me) : merge once whithout introspection useflag and re-merge with introspection. (In reply to comment #5) > Possible workaround (worked for me) : > merge once whithout introspection useflag and re-merge with introspection. Sorry, I mistaken, don't work :( well ... I've met an another problem ... Babl-0.1.gir:27.25-27.25: error: a symbol must be specified <type name="" c:type="Babl*"/> ^ ** (vapigen-0.14:28434): CRITICAL **: vala_unresolved_type_construct_from_symbol: assertion `symbol != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_gir_parser_element_get_type: assertion `orig_type != NULL' failed Babl-0.1.gir:73.23-73.23: error: a symbol must be specified <type name="" c:type="Babl*"/> ^ ** (vapigen-0.14:28434): CRITICAL **: vala_unresolved_type_construct_from_symbol: assertion `symbol != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_gir_parser_element_get_type: assertion `orig_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_method_construct: assertion `return_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_access: assertion `self != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_external: assertion `self != NULL' failed Babl-0.1.gir:98.23-98.23: error: a symbol must be specified <type name="" c:type="Babl*"/> ^ ** (vapigen-0.14:28434): CRITICAL **: vala_unresolved_type_construct_from_symbol: assertion `symbol != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_gir_parser_element_get_type: assertion `orig_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_method_construct: assertion `return_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_access: assertion `self != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_external: assertion `self != NULL' failed Babl-0.1.gir:184.21-184.21: error: a symbol must be specified <type name="" c:type="Babl*"/> ^ ** (vapigen-0.14:28434): CRITICAL **: vala_unresolved_type_construct_from_symbol: assertion `symbol != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_gir_parser_element_get_type: assertion `orig_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_method_construct: assertion `return_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_access: assertion `self != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_external: assertion `self != NULL' failed Babl-0.1.gir:231.21-231.21: error: a symbol must be specified <type name="" c:type="Babl*"/> ^ ** (vapigen-0.14:28434): CRITICAL **: vala_unresolved_type_construct_from_symbol: assertion `symbol != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_gir_parser_element_get_type: assertion `orig_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_method_construct: assertion `return_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_access: assertion `self != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_external: assertion `self != NULL' failed Babl-0.1.gir:244.21-244.21: error: a symbol must be specified <type name="" c:type="Babl*"/> ^ ** (vapigen-0.14:28434): CRITICAL **: vala_unresolved_type_construct_from_symbol: assertion `symbol != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_gir_parser_element_get_type: assertion `orig_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_method_construct: assertion `return_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_access: assertion `self != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_external: assertion `self != NULL' failed Babl-0.1.gir:291.21-291.21: error: a symbol must be specified <type name="" c:type="Babl*"/> ^ ** (vapigen-0.14:28434): CRITICAL **: vala_unresolved_type_construct_from_symbol: assertion `symbol != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_gir_parser_element_get_type: assertion `orig_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_method_construct: assertion `return_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_access: assertion `self != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_external: assertion `self != NULL' failed Babl-0.1.gir:317.21-317.21: error: a symbol must be specified <type name="" c:type="Babl*"/> ^ ** (vapigen-0.14:28434): CRITICAL **: vala_unresolved_type_construct_from_symbol: assertion `symbol != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_gir_parser_element_get_type: assertion `orig_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_method_construct: assertion `return_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_access: assertion `self != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_external: assertion `self != NULL' failed Babl-0.1.gir:324.25-324.25: error: a symbol must be specified <type name="" c:type="Babl**"/> ^ ** (vapigen-0.14:28434): CRITICAL **: vala_unresolved_type_construct_from_symbol: assertion `symbol != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_gir_parser_element_get_type: assertion `orig_type != NULL' failed Babl-0.1.gir:327.25-327.25: error: a symbol must be specified <type name="" c:type="Babl**"/> ^ ** (vapigen-0.14:28434): CRITICAL **: vala_unresolved_type_construct_from_symbol: assertion `symbol != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_gir_parser_element_get_type: assertion `orig_type != NULL' failed Babl-0.1.gir:333.21-333.21: error: a symbol must be specified <type name="" c:type="Babl*"/> ^ ** (vapigen-0.14:28434): CRITICAL **: vala_unresolved_type_construct_from_symbol: assertion `symbol != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_gir_parser_element_get_type: assertion `orig_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_method_construct: assertion `return_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_access: assertion `self != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_external: assertion `self != NULL' failed Babl-0.1.gir:346.21-346.21: error: a symbol must be specified <type name="" c:type="Babl*"/> ^ ** (vapigen-0.14:28434): CRITICAL **: vala_unresolved_type_construct_from_symbol: assertion `symbol != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_gir_parser_element_get_type: assertion `orig_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_method_construct: assertion `return_type != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_access: assertion `self != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_symbol_set_external: assertion `self != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_code_node_get_attribute_string: assertion `self != NULL' failed ** (vapigen-0.14:28434): CRITICAL **: vala_code_node_get_attribute_string: assertion `self != NULL' failed .... (and any lines more.) Generation failed: 12 error(s), 0 warning(s) How to fix it? (In reply to comment #7) > well ... I've met an another problem ... > > Babl-0.1.gir:27.25-27.25: error: a symbol must be specified > <type name="" c:type="Babl*"/> > ^ [...] > > ** (vapigen-0.14:28434): CRITICAL **: > vala_unresolved_type_construct_from_symbol: assertion `symbol != NULL' failed > > > How to fix it? Your problem apears 1 step after ours :-/ But some kind related (it's about an empty "name" in the file) What is your version of dev-libs/gobject-introspection ? Can you attach full build.log, and Babl-0.1.gir? Perhaps we could figure out why you can go 1 step further... For your problem, try to launch this command in the workdir : /usr/bin/vapigen --library=libbabl-0.1 Babl-0.1.gir and see if it's better than : /usr/bin/vapigen --library=babl-0.1 Babl-0.1.gir Created attachment 312195 [details, diff] patch to fix gir generation from OpenSuse package[1] Seong-ho, Cho : according to OpenSuse changelog, your problem seem to be the vala useflag [1] http://rpmfind.net/linux/RPM/opensuse/factory/x86_64/babl-devel-0.1.10-1.2.x86_64.html (In reply to comment #9) > Created attachment 312195 [details, diff] [details, diff] > patch to fix gir generation from OpenSuse package[1] This patch does fix the issue for me (In reply to comment #10) > (In reply to comment #9) > > Created attachment 312195 [details, diff] [details, diff] [details, diff] > > patch to fix gir generation from OpenSuse package[1] > > This patch does fix the issue for me Can you post your build.log after patch applyed ? it would be really nice if this will be fix soon. this package blocks so lot of other pakages. thanks Created attachment 313273 [details] babl-0.1.10 build log after applying upstream patch from comment #3 I was able to emerge babl-0.1.10 without the introspection USE flag, but I am not able to now re-emerge it with the introspection USE flag. So I attempted the patch(es) here. I first tried to apply the patch submitted with comment #9, and it fails with, "Local patch babl-0.1.10-fix-gir-build.patch does not fit". I then tried to apply the upstream patch referenced in comment #3, but the emerge fails when attempting to apply the babl-0.1.6-introspection.patch. I then commented out the babl-0.1.6-introspection.patch, so that the upstream patch from comment #3 applies, and the emerge gets past the patch phase, only to die later with the same message posted originally here, "ERROR:girepository/girnode.c:1031:find_entry_node: assertion failed: (strlen (name) > 0)". This is the complete babl-0.1.10 build log, applying the upstream patch from comment #3, and commenting out the babl-0.1.6-introspection.patch, from my system, FWIW. The OpenSuse patch attached works for me. Some info on how to apply the attached OpenSUSE patch would be handy. I've tried a number of variations including removing the existing introspection patch and it doesn't apply for me. Successful patchers - care to share? Created attachment 313583 [details]
ebuild with opensuse patch
To people that don't know how to use the patch, here is the ebuild that use it.
name the patch to files/babl-0.1.10-fix-gir-build.patch
Created attachment 313597 [details] failed patch log using new ebuild and patch Using the submitted ebuild from comment #16 and the patch from comment #3 on my system, the emerge fails applying the babl-0.1.10-fix-gir-build.patch. What's odd is that if I do a manual ebuild /usr/portage/media-libs/babl/babl-0.1.10.ebuild unpack, then prepare, and then edit the corresponding babl/Makefile.am file and insert at line 98; --identifier-prefix= --symbol-prefix=babl \ and then do an ebuild /usr/portage/media-libs/babl/babl-0.1.10.ebuild compile, I still get a failure with; ERROR:girepository/girnode.c:1031:find_entry_node: assertion failed: (strlen (name) > 0) (In reply to comment #16) > Created attachment 313583 [details] > ebuild with opensuse patch > > To people that don't know how to use the patch, here is the ebuild that use > it. > name the patch to files/babl-0.1.10-fix-gir-build.patch The patch doesn't directly line up with the sources - manually patching it into an untarred source fails completely. This means that people who claim success are performing additional steps they're not expressing here, and which would be helpful. Created attachment 314203 [details, diff]
babl-0.1.10-gir-build-fix.patch
Ok, here's a patch that applies after babl-0.1.6-introspection.patch. This now moves the failure from USE="introspection" to USE="introspection vala".
As pointed out, after this patch is applied, valagen complains about all uses of Babl* (a pointer to a Babl object). It's not clear how to deal with this, but at least it provides a little progress (and allows people to build with introspection but not with introspection AND vala).
Please note, even with the appropriate introspection files built, it reveals a separate bug in gegl with USE="introspection", so will not help with building gegl.
I can confirm that I was able to emerge media-libs/babl-0.1.10 with the introspection USE flag, using the patch from comment #19. However, I could not use it with portage's localpatch facility because it applies the babl-0.1.10-gir-build-fix.patch before the babl-0.1.6-introspection.patch. Adding it to my local portage overlay and editing the ebuild so that the babl-0.1.10-gir-build-fix.patch, applies after the babl-0.1.6-introspection.patch, did work. Additionally bug 416587 has a patch that, when combined with a manual make, ebuild compile and merge process, worked for emerging media-libs/gegl-0.2.0 with the introspection USE flag, on my system. Created attachment 314897 [details]
babl-0.1.10-r1.ebuild
Comment on attachment 314897 [details]
babl-0.1.10-r1.ebuild
Fixed ebuild with introspection patch in the right order
(In reply to comment #20) Applying the patch in the right order works for me too. I added a patch reflecting this. Also building gegl with introspection and the proposed patch and manually restarting the make process worked for me. Yes, the patch fixed the babl build for me. Thanks :-) Works like a charm, thanks :) + 29 Apr 2013; Sebastian Pipping <sping@gentoo.org> babl-0.1.10.ebuild, + +files/babl-0.1.10-g-ir-compiler-crash.patch, + +files/babl-0.1.10-introspection.patch: + Fix build with USE=introspection (bug #413663), patches by upstream and + openSUSE + + 29 Apr 2013; Sebastian Pipping <sping@gentoo.org> base/package.use.mask: + Unmask ~media-libs/babl-0.1.10[introspection] (bug #413663) + + 30 Apr 2013; Sebastian Pipping <sping@gentoo.org> babl-0.1.8.ebuild: + Apply g-ir crash patch to 0.1.8, too (bug #413663) + + 30 Apr 2013; Sebastian Pipping <sping@gentoo.org> base/package.use.mask: + Unmask ~media-libs/babl-0.1.8[introspection] (bug #413663) + Emerging babl-0.1.10 w/o vala support goes ok. As soon as the vala use flag is set and vala is installed babl compile borks. I tried several versions of vala,same result. In the /var/log/portage/media-libs/babl logs I see the gir errors. As far as I'm concerned this is not quite solved yet. Gerard. (In reply to comment #30) > Emerging babl-0.1.10 w/o vala support goes ok. > As soon as the vala use flag is set and vala is installed babl compile borks. > I tried several versions of vala,same result. > In the /var/log/portage/media-libs/babl logs I see the gir errors. > As far as I'm concerned this is not quite solved yet. > Gerard. Agreed, but there is bug #413663 for that now. (In reply to comment #31) > Agreed, but there is bug #413663 for that now. Bug #468208 I mean, sorry. |