grsync_0.5.2-3 failed because:<br><br><pre>checking for gtk+-2.0 >= 2.0.0 hildon-1 hildon-fm-2 libosso... Package gtk+-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `gtk+-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'gtk+-2.0' found Package hildon-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `hildon-1.pc' to the PKG_CONFIG_PATH environment variable No package 'hildon-1' found Package hildon-fm-2 was not found in the pkg-config search path. Perhaps you should add the directory containing `hildon-fm-2.pc' to the PKG_CONFIG_PATH environment variable No package 'hildon-fm-2' found Package libosso was not found in the pkg-config search path. Perhaps you should add the directory containing `libosso.pc' to the PKG_CONFIG_PATH environment variable No package 'libosso' found<br>
configure: error: Library requirements (gtk+-2.0 >= 2.0.0 hildon-1 hildon-fm-2 libosso) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.<br>
</pre>Maybe there are some dependencies requisites which I'm not aware of?<br><br>Luca Donaggio<br><br><div class="gmail_quote">On Mon, Jun 16, 2008 at 4:33 PM, Niels Breet <<a href="mailto:niels@maemo.org">niels@maemo.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi all,<br>
<br>
Currently Ed Bartosh and I are working on taking all source packages from<br>
the extras repository and try to build them on the autobuilder. The goal<br>
of this chinook rebuild effort is to get a set of packages buildable 'from<br>
scratch'.<br>
<br>
Once we are able to build all(most?) packages on chinook, we can try to<br>
automatically build them for diablo. So we can have a lot of packages in<br>
the diablo repository at release of diablo.<br>
<br>
There is a web page[1] up with the first run, which was done over the<br>
weekend. All packages are listed in build order, based on dependencies,<br>
with their build results for i386 and armel. If a package build failed, a<br>
link to the build log is provided.<br>
<br>
If you provide a source package in extras, please check if your package is<br>
building OK. If you only provide binary packages in extras, we would<br>
like to encourage you to provide source packages too! We could really use<br>
some help from the community in pushing towards 100% OK build of every<br>
package in extras.<br>
<br>
When you have updated your package to fix the issues, please use the<br>
'request rebuild' option on the packages list. This gives us the<br>
opportunity to track changes as a result of the list. We will rebuild<br>
packages on a regular interval and post a summary to this list. Let's see<br>
if we can get all packages to build!<br>
<br>
<br>
--<br>
Niels Breet<br>
<a href="http://maemo.org" target="_blank">maemo.org</a> webmaster<br>
<br>
<br>
[1]<br>
<a href="https://garage.maemo.org/extras-assistant/maemo_extras_chinook_rebuild.php" target="_blank">https://garage.maemo.org/extras-assistant/maemo_extras_chinook_rebuild.php</a><br>
<br>
<br>
PS:<br>
Please note that due to a build failure in python-2.5, all packages that<br>
depend on python fail. So after this failure is fixed, a lot more packages<br>
will build OK. I will contact the indt guys to get this sorted.<br>
<br>
<br>
_______________________________________________<br>
maemo-developers mailing list<br>
<a href="mailto:maemo-developers@maemo.org">maemo-developers@maemo.org</a><br>
<a href="https://lists.maemo.org/mailman/listinfo/maemo-developers" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-developers</a><br>
</blockquote></div><br>