After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 640058 - Build failure due missing libdmapsharing-3.0 package
Build failure due missing libdmapsharing-3.0 package
Status: RESOLVED INCOMPLETE
Product: libdmapsharing
Classification: Other
Component: DAAP Client
git master
Other Linux
: Normal blocker
: ---
Assigned To: W. Michael Petullo
W. Michael Petullo
Depends on:
Blocks:
 
 
Reported: 2011-01-20 13:07 UTC by Luca Ferretti
Modified: 2011-05-18 04:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Luca Ferretti 2011-01-20 13:07:27 UTC
From build log of a fresh checkout (jhbuild sandbox)


/opt/gnome3/bin/valac --vapidir=../vala --pkg gee-1.0 --pkg gstreamer-0.10 --pkg libdmapsharing-3.0 --pkg libsoup-2.4 --pkg glib-2.0 dacplisten.vala vala-dmap-db.vala vala-dmap-container-db.vala -C
error: Package `libdmapsharing-3.0' not found in specified Vala API directories or GObject-Introspection GIR directories
Compilation failed: 1 error(s), 0 warning(s)


(sorry for wrong component, maybe adding a "geneal" one could be a good idea)
Comment 1 W. Michael Petullo 2011-01-20 15:19:27 UTC
This has now been addressed in Git master. Would you please test these changes?
Comment 2 Luca Ferretti 2011-01-20 18:23:04 UTC
That specific issue was resolved, but now I've a different blocker:

make[2]: Entering directory `/home/betatester/checkout/gnome/libdmapsharing/vala'
PKG_CONFIG_PATH=..:/opt/gnome3/lib64/pkgconfig:/opt/gnome3/share/pkgconfig:/usr/share/pkgconfig:/usr/lib64/pkgconfig /opt/gnome3/bin/vala-gen-introspect libdmapsharing-3.0 libdmapsharing-3.0-daap
find: `/opt/gnome3/include/libdmapsharing-3.0/libdmapsharing/': No such file or directory
find: `/opt/gnome3/lib64/libdmapsharing-3.0.so': No such file or directory
ERROR: Need at least one header file.
make[2]: *** [libdmapsharing-3.0-daap/libdmapsharing-3.0.gi] Error 1
make[2]: Leaving directory `/home/betatester/checkout/gnome/libdmapsharin

It seems build system is unable to use "local" copy of libdmapsharing-3.0.so

However, running make a second time, I've a different error message


make[2]: Entering directory `/home/betatester/checkout/gnome/libdmapsharing/vala'
/opt/gnome3/bin/vapigen --pkg=libsoup-2.4 --pkg=glib-2.0 --pkg=gio-2.0 --pkg=gstreamer-0.10 --library libdmapsharing-3.0-daap libdmapsharing-3.0-daap/libdmapsharing-3.0.gi
error: Unable to parse GIDL file: Error on line 1 char 1: Document was empty or contained only whitespace
Generation failed: 1 error(s), 0 warning(s)
Comment 3 W. Michael Petullo 2011-01-21 00:25:50 UTC
Can you try 2.9.3? I decided to ship libdmapsharing-3.0.vapi in the tarball and avoid regenerating it unless in configured with --enable-maintainer-mode.
Comment 4 Luca Ferretti 2011-02-03 16:03:27 UTC
Hi, sorry for the lag. I tried 2.9.3 from tar.gz. It also fails with following message

PKG_CONFIG_PATH=..:/opt/gnome3/lib64/pkgconfig:/opt/gnome3/share/pkgconfig:/usr/share/pkgconfig:/usr/lib64/pkgconfig:/usr/lib/pkgconfig /opt/gnome3/bin/vala-gen-introspect libdmapsharing-3.0 libdmapsharing-3.0-daap
find: "/opt/gnome3/include/libdmapsharing-3.0/libdmapsharing/": File o directory non esistente
find: "/opt/gnome3/lib64/libdmapsharing-3.0.so": File o directory non esistente
ERROR: Need at least one header file.

I've also tried to manually force --enable-maintainer-mode (it's automatically used running autogen.sh, the way I was using on git clone), but no luck :(

I hope we can have a fine building libdmapsharing from git, in order to add it to jhbuild and use for rhythmbox build.
Comment 5 W. Michael Petullo 2011-02-03 17:29:05 UTC
When maintainer-mode is enabled, libdmapsharing tries to build its Vala API description file (vala/libdmapsharing-3.0.vapi). In order to do this, libdmapsharing must already be installed to satisfy vala/libdmapsharing-3.0-daap/libdmapsharing-3.0.files. I'm not sure how to get around this.

Can you try running "./configure --disable-maintainer-mode" after autogen.sh?

I am not very familiar with jhbuild. Are you aware of any other packages that ship their own Vala API description file? I'd like to see how they handle this.
Comment 6 Akhil Laddha 2011-03-17 04:32:27 UTC
Luca, were you able to build successfully after following comment#5 ?