Summary: | dev-ruby/ruby-glib2-0.19.1 fail to compile when broken pkg-config files are found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cănărău Constantin <canarauc> |
Component: | Current packages | Assignee: | Gentoo Ruby Team <ruby> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | Adrian.Bassett, ashutiwary, bbutscheidt, c.apeltauer, dan, feinorgh, gem, joost.ruis, laurento.frittella, mlspamcb, n-roeser, quazgar, robert.bradbury, tetromino, waynedpj, willard.dawson |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | https://bugs.freedesktop.org/show_bug.cgi?id=26615 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 283534, 294182, 309749, 321525 | ||
Bug Blocks: |
Description
Cănărău Constantin
2009-09-14 19:03:16 UTC
Same problem for me. Package ming was not found in the pkg-config search path. Perhaps you should add the directory containing `ming.pc' to the PKG_CONFIG_PATH environment variable Package 'ming', required by 'Autotrace', not found this is your problem (for the trace log provided, for others, it will be other pkg-config files). Make sure your pkg-config file in /usr/lib/pkgconfig are good, and if you got stuff installed in /usr/local, fix it. Open bugs for eventual packages that install broken pkg-config files. *** Bug 285426 has been marked as a duplicate of this bug. *** For me, this is caused by bug 283534 (media-gfx/autotrace installs invalid .pc file). Please add 283534 to the "depends on" list for this bug. I did a emerge -e world (CPU and gcc changed) and problem it's solved. It's seems that broken package (ming related, media-gfx/autotrace perhaps) was repaired meanwhile. Unfortunately I can't provide any new info to help others. Maybe you should close this bug. Thank you! We should leave this bug open until we've fixed the fragile handling of pkg-config files by the ruby-gnome2 code. It should not break so easily. For me dev-ruby/ruby-glib2-0.19.1 fails to compile because of this: Package 'glipper' has no Name: field It seems x11-misc/glipper is responsible; pkg-config --list-all | grep glipper Package 'glipper' has no Name: field Hope that helps. Here I have ~amd64 arch. I end up removing x11-misc/glipper and media-sound/ripperx. Otherwise the following ones fail to emerge in order: dev-ruby/ruby-glib2-0.19.1 dev-ruby/ruby-pango-0.19.1 dev-ruby/ruby-gdkpixbuf2-0.19.1 dev-ruby/ruby-gtk2-0.19.1 pkg-config --list-all | grep ripperx Variable 'libdir' not defined in '/usr/lib64/pkgconfig/ripperX.pc' Guys we appreciate you tracked down the issues, but _please_ open *new* bugs for those. We don't go around fixing others' packages. This bug will be kept open because we do have to fix the fragility in the current ruby-pkgconfig code, but we won't be fixing hese things ourselves. Open new bugs, mark them as blockers of this one, and then the right people will pick them up. Thank you! *** Bug 288455 has been marked as a duplicate of this bug. *** *** Bug 288448 has been marked as a duplicate of this bug. *** *** Bug 297557 has been marked as a duplicate of this bug. *** *** Bug 298196 has been marked as a duplicate of this bug. *** This might be a problem with pkgconfig itself, so I'm also cc'ing the gnome herd. pkg-config aborts when it finds a broken .pc file. Installing e.g. glipper and then running pkg-config --list-all causes pkg-config to abort and not list all the packages. Adding --silence-errors seems to avoid this problem, so that seems like a good solution for the ruby-gnome packages. (In reply to comment #14) > Adding --silence-errors seems to avoid this problem, so that seems like a good > solution for the ruby-gnome packages. Unfortunately this only avoids printing the error, but pkg-config still doesn't list all properly installed .pc files this way. *** Bug 298417 has been marked as a duplicate of this bug. *** Note that the ming.pc file has changed to libming.pc in the latest release of media-libs/ming in Gentoo (0.4.0rc2). Symlinking /usr/lib64/pkgconfig/ming.pc -> libming.pc made ruby-glib2 build on my system. Until a proper fix for this bug comes along, this might help. *** Bug 301232 has been marked as a duplicate of this bug. *** pkg-config is a dev package, not an end-user tool. Packages that install broken .pc files should be fixed. Maybe pkg-config should print warnings or something if it finds broken files, but that's way beyond the scope of the current code. IMHO, glipper should be fixed. Removing CC, there's nothing for us to do. Thanks Glipper has been fixed in glipper-1.0-r3. Now having issues with sci-physics/bullet installing a broken bullet.pc file. I notice that pkg-config generates the whole list, but it also seems to generate an error line "Variable 'ROOT' not defined in '/usr/lib64/pkgconfig/bullet.pc'" that confuses ruby. Could the error line be ignored somehow? not sure about pkg-config handling being fixed, but unmasking media-gfx/autotrace-0.31.1-r4 (~amd64) along with the stable version of media-libs/ming-0.4.0_rc2 and re-emerging seems to get past this problem with rub-glib2 not compiling for me. check out bug #283534 for more info. (In reply to comment #22) > I notice that pkg-config generates the whole list, but it also seems to > generate an error line "Variable 'ROOT' not defined in > '/usr/lib64/pkgconfig/bullet.pc'" that confuses ruby. Could the error line be > ignored somehow? No, the problem is that pkg-config stops executing as soon as it encounters an error, so it does not in fact generate the whole list of installed packages. If one of the packages needed by the ruby-gnome2 packages happens to come after that this problem occurs. Filed upstream. Checked but not yet fixed in pkgconfig-0.25. ruby-gnome2 now uses the separate dev-ruby/pkg-config package, which handles pkg-config files in ruby instead of calling out to the broken C tool. This version is now (being marked) stable. |