On Mon, Apr 8, 2013 at 1:35 PM, Andrew Hoffman <andy.hoffma...@gmail.com> wrote: > > > > On Mon, Apr 8, 2013 at 1:30 PM, Canek Peláez Valdés <can...@gmail.com> > wrote: >> >> On Mon, Apr 8, 2013 at 1:10 PM, Andrew Hoffman <andy.hoffma...@gmail.com> >> wrote: >> > >> > >> > >> > On Mon, Apr 8, 2013 at 1:02 PM, Canek Peláez Valdés <can...@gmail.com> >> > wrote: >> >> >> >> On Mon, Apr 8, 2013 at 12:54 PM, Andrew Hoffman >> >> <andy.hoffma...@gmail.com> wrote: >> >> > Canek, >> >> > I have those files in /usr/lib/pkgconfig I do not have a /usr/lib64 >> >> > >> >> > lapy lib # locate telepathy-glib.pc >> >> > /usr/lib/pkgconfig/telepathy-glib.pc >> >> > lapy lib # locate dbus-glib-1.pc >> >> > /usr/lib/pkgconfig/dbus-glib-1.pc >> >> > lapy lib # locate gio-2.0.pc >> >> > /usr/lib/pkgconfig/gio-2.0.pc >> >> > lapy lib # locate gee-1.0.pc >> >> > /usr/lib/pkgconfig/gee-1.0.pc >> >> > >> >> > How would I tell if they are damaged if that is indeed the case? >> >> >> >> Don't top-post, please. Sorry, I messed up the files; you don't need >> >> the pkgconfig files (*.pc), you need the Vala API files (*.vapi). You >> >> need: >> >> >> >> /usr/share/vala/vapi/telepathy-glib.vapi >> >> /usr/share/vala-0.18/vapi/dbus-glib-1.vapi >> >> /usr/share/vala-0.18/vapi/gio-2.0.vapi >> >> /usr/share/vala/vapi/gee-1.0.vapi >> >> >> >> Depending on how many Vala compiler versions you have, you can have >> >> several of the second and the third; for example I have: >> >> >> >> /usr/share/vala-0.12/vapi/dbus-glib-1.vapi >> >> /usr/share/vala-0.14/vapi/dbus-glib-1.vapi >> >> /usr/share/vala-0.16/vapi/dbus-glib-1.vapi >> >> /usr/share/vala-0.18/vapi/dbus-glib-1.vapi >> >> /usr/share/vala-0.20/vapi/dbus-glib-1.vapi >> >> >> >> Check if you have the four vapi files, and that the ones for >> >> dbus-glib-1 and gio-2.0 exists for all your versions of the Vala >> >> compiler. >> >> >> >> Regards. >> >> -- >> >> Canek Peláez Valdés >> >> Posgrado en Ciencia e Ingeniería de la Computación >> >> Universidad Nacional Autónoma de México >> >> >> > >> > Guess gmail defaults to top post so its what I use:/ >> > >> > Anyhow I have these files: >> > >> > lapy lib # locate telepathy-glib.vapi >> > /usr/share/vala/vapi/telepathy-glib.vapi >> > lapy lib # locate dbus-glib-1.vapi >> > /usr/share/vala-0.12/vapi/dbus-glib-1.vapi >> > /usr/share/vala-0.14/vapi/dbus-glib-1.vapi >> > /usr/share/vala-0.16/vapi/dbus-glib-1.vapi >> > /usr/share/vala-0.18/vapi/dbus-glib-1.vapi >> > lapy lib # locate gio-2.0.vapi >> > /usr/share/vala-0.12/vapi/gio-2.0.vapi >> > /usr/share/vala-0.14/vapi/gio-2.0.vapi >> > /usr/share/vala-0.16/vapi/gio-2.0.vapi >> > /usr/share/vala-0.18/vapi/gio-2.0.vapi >> > lapy lib # locate gee-1.0.vapi >> > /usr/share/vala/vapi/gee-1.0.vapi >> >> I see the error now. The problem is that the class GLib.Bytes is >> defined in glib-2.0.vapi for valac 0.16, 0.18 and 0.20, but not for >> valac 0.12 nor 0.14. The latest version of telepahy-glib uses >> GLib.Bytes, so it dependencies need to be compiled with a newer >> version of valac. >> >> Can you try to emerge folks as follows: >> >> VALA_MIN_API_VERSION="0.16" emerge dev-libs/folks >> >> If that fails, what version of telepathy-glib do you have installed? >> >> Regards. >> -- >> Canek Peláez Valdés >> Posgrado en Ciencia e Ingeniería de la Computación >> Universidad Nacional Autónoma de México >> > > that did fail: > > lapy portage # VALA_MIN_API_VERSION="0.16" emerge dev-libs/folks > Calculating dependencies... done! > >>>> Verifying ebuild manifests > >>>> Emerging (1 of 1) dev-libs/folks-0.4.3 > * folks-0.4.3.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... > [ ok ] >>>> Unpacking source... >>>> Unpacking folks-0.4.3.tar.bz2 to >>>> /var/tmp/portage/dev-libs/folks-0.4.3/work >>>> Source unpacked in /var/tmp/portage/dev-libs/folks-0.4.3/work >>>> Preparing source in >>>> /var/tmp/portage/dev-libs/folks-0.4.3/work/folks-0.4.3 ... > * Fixing OMF Makefiles ... > [ ok ] > * Disabling deprecation warnings ... > [ ok ] > * Running elibtoolize in: folks-0.4.3/ > * Applying portage/1.2.0 patch ... > * Applying sed/1.5.6 patch ... > * Applying as-needed/2.2.6 patch ... >>>> Source prepared. >>>> Configuring source in >>>> /var/tmp/portage/dev-libs/folks-0.4.3/work/folks-0.4.3 ... > (removed) > checking pkg-config is at least version 0.21... yes > checking for GLIB... yes > checking for GMODULE... yes > checking for GIO... yes > checking for DBUS_GLIB... yes > checking for GEE... yes > checking for TP_GLIB... yes > checking for valac... /usr/bin/valac-0.12 > checking /usr/bin/valac-0.12 is at least version 0.11.6... yes > checking for vapigen... /usr/bin/vapigen-0.12 > checking for telepathy-glib dbus-glib-1 gio-2.0 gee-1.0 vala bindings... > configure: error: Package requirements were not met: telepathy-glib > dbus-glib-1 > gio-2.0 > gee-1.0 > > warning: D-Bus GLib is deprecated, use GDBus > telepathy-glib.vapi:1326.36-1326.45: error: The type name `GLib.Bytes' could > not be found > > Consider adjusting the XDG_DATA_DIRS environment variable if you > installed bindings in a non-standard prefix. > > > !!! Please attach the following file when seeking support: > !!! /var/tmp/portage/dev-libs/folks-0.4.3/work/folks-0.4.3/config.log > * ERROR: dev-libs/folks-0.4.3 failed (configure phase): > * econf failed > * > * Call stack: > * ebuild.sh, line 93: Called src_configure > * environment, line 3005: Called gnome2_src_configure > * environment, line 2258: Called econf '--disable-silent-rules' > '--enable-import-tool' '--enable-inspect-tool' '--enable-vala' > 'VALAC=/usr/bin/valac-0.12' 'VAPIGEN=/usr/bin/vapigen-0.12' '--disable-docs' > '--disable-Werror' > * phase-helpers.sh, line 521: Called die > * The specific snippet of code: > * die "econf failed" > * > * If you need support, post the output of `emerge --info > '=dev-libs/folks-0.4.3'`, > * the complete build log and the output of `emerge -pqv > '=dev-libs/folks-0.4.3'`. > * The complete build log is located at > '/var/tmp/portage/dev-libs/folks-0.4.3/temp/build.log'. > * The ebuild environment file is located at > '/var/tmp/portage/dev-libs/folks-0.4.3/temp/environment'. > * Working directory: > '/var/tmp/portage/dev-libs/folks-0.4.3/work/folks-0.4.3' > * S: '/var/tmp/portage/dev-libs/folks-0.4.3/work/folks-0.4.3' > >>>> Failed to emerge dev-libs/folks-0.4.3, Log file: > >>>> '/var/tmp/portage/dev-libs/folks-0.4.3/temp/build.log' > > * Messages for package dev-libs/folks-0.4.3: > > * ERROR: dev-libs/folks-0.4.3 failed (configure phase): > * econf failed > * > * Call stack: > * ebuild.sh, line 93: Called src_configure > * environment, line 3005: Called gnome2_src_configure > * environment, line 2258: Called econf '--disable-silent-rules' > '--enable-import-tool' '--enable-inspect-tool' '--enable-vala' > 'VALAC=/usr/bin/valac-0.12' 'VAPIGEN=/usr/bin/vapigen-0.12' '--disable-docs' > '--disable-Werror' > * phase-helpers.sh, line 521: Called die > * The specific snippet of code: > * die "econf failed" > * > * If you need support, post the output of `emerge --info > '=dev-libs/folks-0.4.3'`, > * the complete build log and the output of `emerge -pqv > '=dev-libs/folks-0.4.3'`. > * The complete build log is located at > '/var/tmp/portage/dev-libs/folks-0.4.3/temp/build.log'. > * The ebuild environment file is located at > '/var/tmp/portage/dev-libs/folks-0.4.3/temp/environment'. > * Working directory: > '/var/tmp/portage/dev-libs/folks-0.4.3/work/folks-0.4.3' > * S: '/var/tmp/portage/dev-libs/folks-0.4.3/work/folks-0.4.3'
Yeah, it ignored the VALA_MIN_API_VERSION environment variable. I see now that they explicitly require valac-0.12, so it's going to fail anyhow. > Telepathy-glib version: > net-libs/telepathy-glib-0.20.1-r1 Same as me. But I have folks 0.9.1, which uses at least valac-0.18. It is a legitimate bug; telepathy-glib installs a vapi file which requires the use of GLib.Bytes, which is not available in the glib-2.0.vapi file for valac 0.12. And there are no older versions of telepathy-glib in the tree. What does "equery depends dev-libs/folks" says? Maybe you can get rid of the dependency. Also, if you don't use empathy, maybe you can get away with putting folks in package.provided. Another workaround: you can put the folks ebuild in a personal overlay, and change the following: VALAC=$(type -p valac-0.12) VAPIGEN=$(type -p vapigen-0.12) to VALAC=$(type -p valac-0.16) VAPIGEN=$(type -p vapigen-0.16) Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
