@Lanoxx You did not mention you tried 'jhbuild sysdeps --install'. Run
that too. It might save you some time finding all the devel packages
in Synaptic.
Am 24.12.2012 um 02:37 schrieb Emily Gonyer :
> IME that means you need to go through and find all of those packages -
> my suggestion is to i
Hello,
On Sun, Dec 23, 2012 at 09:53:36PM +0100, Lanoxx wrote:
> I am using jhbuild and trying to compile anjuta (with anjuta-extras)
> to test a patch that was applied recently on anjuta-extras.
>
> jhbuild build
The gnome-love list would have been a better place, but anyway, you must
mention
Hi,
I have already run jhbuild sysdeps --install, and also ran jhbuild build
anjuta, with the first one I get this output:
I: Using apt-file to search for providers; this may be slow. Please wait.
I: No native package found for alsa (/alsa.pc)
I: No native package found for libv4l (/libv4l2.p
try sudo apt-get install wireless-tools libicu-dev - they are in
ubuntu's repos and should be a new enough version.
On Mon, Dec 24, 2012 at 8:29 AM, Lanoxx wrote:
> Hi,
>
> I have already run jhbuild sysdeps --install, and also ran jhbuild build
> anjuta, with the first one I get this output:
>
>
Both packages are installed, as I wrote, there is a bug in libicu-dev
4.1.1 where the pkg-config files are not available, this bug is only
fixed in 4.1.1-10 which is not going to be backported to Ubuntu 12.10
which currently has 4.1.1-8 (which still has this bug). As for wireless
tools, it is a
Besides that, I am wondering, why anjuta needs wireless tools and libicu.
On 24/12/12 18:21, Lanoxx wrote:
Both packages are installed, as I wrote, there is a bug in libicu-dev
4.1.1 where the pkg-config files are not available, this bug is only
fixed in 4.1.1-10 which is not going to be backpo
1. You could just install the updated deb file:
http://packages.debian.org/sid/libicu-dev#pdownload
2. Also if you have trouble with finding .pc files for packages that you
believe you had installed, make sure that your PKG_CONFIG_PATH variable is
set properly.
(In debian I had to put the followin