Stable gnome-extra/libgda-4.1.0 #298201 for Anjuta compile. Anjuta 2.28.2 emerge failed due to missing libgda.h file. Noted with and upstream have issued patch. Reproducible: Always Steps to Reproduce: 1. emerge =dev-util/anjuta-2.28.2.0 also libgda.h missing after>> 2. emerge libgda Actual Results: Abbreviated: In file included from ../symbol-db-engine-core.h:33, from ../symbol-db-engine.h:32, from benchmark.c:4: ../symbol-db-engine-iterator.h:29:27: error: libgda/libgda.h: No such file or directory benchmark.c: In function ‘main’: benchmark.c:35: warning: implicit declaration of function ‘gda_init’ benchmark.c:35: warning: nested extern declaration of ‘gda_init’ make[4]: *** [benchmark.o] Error 1 make[4]: *** Waiting for unfinished jobs.... ../symbol-db-engine-core.c:118:27: error: libgda/libgda.h: No such file or directory ../symbol-db-engine-core.c: In function ‘sdb_engine_execute_unknown_sql’: ../symbol-db-engine-core.c:321: warning: implicit declaration of function ‘gda_connection_statement_execute’ ../symbol-db-engine-core.c:321: warning: nested extern declaration of ‘gda_connection_statement_execute’ Expected Results: anjuta 2.28.2 install without error for missing libgda.h Noted with and upstream have issued patch. http://mail.gnome.org/archives/commits-list/2010-January/msg05857.html
Created attachment 223413 [details, diff] upstream patch to install libgda.h
Created attachment 223415 [details, diff] patch for libgda ebuild
Created attachment 223421 [details, diff] use tabs for indentation, not spaces
*** Bug 310509 has been marked as a duplicate of this bug. ***
Fixed. Thanks
how was this fixed ? I don't see any commited changes.
(In reply to comment #3) > Created an attachment (id=223421) [details] > use tabs for indentation, not spaces > Both patches worked for me. Had the same problem compiling anjuta before.
+*libgda-4.1.4-r1 (31 Mar 2010) + + 31 Mar 2010; Gilles Dartiguelongue <eva@gentoo.org> + +libgda-4.1.4-r1.ebuild, +files/libgda-4.1.4-install-header.patch: + Install missing header file, bug #308793. Fixed, thanks for reporting and providing a patch.