anjuta configuration - both tarball and rpm
 

If I attempt to use anjuta 1.2.2 rpm from Mandrake/Contrib, I get caught up short with:
anjuta:7749 WARNING Cannot execute command WANT_AUTOCONF-2.5=1
The system has autoconf2.1 2.13-21 and autoconf2.5 2.59-6 installed.

So, I resorted to downloading a tarball for anjuta 1.2.2, but this time I can't complete the configuration because it cannot find vte.pc. I can't find it either, yet there is a vte in /usr/bin and vte directories in both /usr/lib and /usr/share - all pretty standard locations.

Two strikes and I'm out, I guess!

Anyone able to offer some help with this?

(I had some trouble with anjuta back in April, but it resolved itself over a few days, so it appears to me that updates for the contrib rpms are not keeping pace with 'cooker'. Its for this reason that I thought it best to build anjuta from tarball in the future as we will be relying heavily on anjuta in the future.

Many thianks.

George

"So, I resorted to downloading a tarball for anjuta 1.2.2, but this time I can't complete the configuration because it cannot find vte.pc. I can't find it either, yet there is a vte in /usr/bin and vte directories in both /usr/lib and /usr/share - all pretty standard locations."

You may be stumbling over some trash left from your unsuccessful attemp to install the rpm. Try:
rpm -e anjuta
keep repeating the command until rpm tells you that anjuta is not install. The try the compile again.

------------------------------
Steve Stites

Hi, and thanks for responding.

rpm -e anjuta gives no response, which I'd have expected. And the find utility cannot locate anjuta anywhere except in the expansion of the tarball.

I suppose the next step will be to take out the offending vte packages and re-install them????

"rpm -e anjuta gives no response, which I'd have expected."

In the grand tradition of Unix no response means that the command worked. You may have multiple copies of anjuta in the rpm data base. Keep repeating:
rpm -e anjuta
until it gives you the error message that anjuta is not installed.

"And the find utility cannot locate anjuta anywhere except in the expansion of the tarball."

But it is still possible to have anjuta related information in the rpm data base even if anjuta does not exist anywhere else. find does not search the records in the rpm data base.

"I suppose the next step will be to take out the offending vte packages and re-install them????"

It is possible that the vte package install is screwed up. It is also possible that you have mismatched vte and anjuta versions. But I suggest that you first try to fix anjuta without messing with vte.

-------------------
Steve Stites