Re: [Ekiga-list] Unable to compile 3.2.4 on Ubuntu Jaunty
- From: "Christian Jaeger" <pflanze gmx ch>
- To: Ekiga mailing list <ekiga-list gnome org>, ekiga-list gnome org
- Subject: Re: [Ekiga-list] Unable to compile 3.2.4 on Ubuntu Jaunty
- Date: Sun, 21 Jun 2009 20:31:19 +0200
> I followed the wiki page at:
> http://wiki.ekiga.org/index.php/Compile_your_own_SVN_version_of_Ekiga_on_Ubuntu
Interesting, in that this suggests to check out Ekiga from SVN. I've tried "svn co http://svn.gnome.org/svn/ekiga/trunk ekiga" and compared to what I got from Git. It seems that the SVN repo (r7862) has last been updated on April 15, and that this version corresponds to Git commit 807740337f4d9853878b9f2419abe40ddbe2a406, and that from that point in time on the project has transitioned to using Git (r7862 and older has been imported into Git). This means that the above wiki page should be updated to check out Ekiga from Git instead, as shown on http://wiki.ekiga.org/index.php/Download_Ekiga_sources (ptlib and opal are still tracked in SVN as it seems).
(Also note that you might prefer to check out the "gnome-2-26" branch from Git, as mentioned on Download_Ekiga_sources--although that's the branch I'm currently using and running into sound problems with (haven't checked "master" yet)).
>
> And ran autogen.sh with - - prefix=/usr - - sysconfdir=/etc/ exactly as
> described in the wiki. I tried the command Paul suggested:
> cd /usr/bin
> export LD_LIBRARY_PATH=/usr/lib
> And it completed without error, but I still get the following error in
> terminal no matter where I try it from.
>
> spencer spencer-desktop:/usr/bin$ ekiga
> The program 'ekiga' is currently not installed. You can install it by
> typing:
> sudo apt-get install ekiga
> bash: ekiga: command not found
>
> spencer spencer-desktop:/usr/bin$ ./ekiga
> bash: ./ekiga: No such file or directory
So ekiga is not in the place it should be (which should be where you tried). This sounds to me like you forgot to run the "sudo make install" step, or that this step failed.
Run "sudo make install ; echo $?", this will print the exit code of the make install step in the end, which should be 0 if everything went ok; otherwise, look at the messages from the make install, it should give a clue about what went wrong (disk full, maybe?).
> As I'm sure is painfully obvious already, I come from primarily an
> MS/Windows background and am still pretty lost in Linux/Ubuntu.
Welcome in the new land.
Christian.
--
GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate und Telefonanschluss
für nur 17,95 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]