Eugen Dedu wrote:
H.S. wrote:
Mateusz Kaduk wrote:
2009/6/11 H.S. <[email protected]>:
Why do you say it makes no sense?
Well it makes sense and is useful, but doing profile is really fast
and should reveal exactly the part of code causing problems that is
using the most CPU cycles.
Looks interesting.
Indeed.
Is there any problem with the one available in Debian?
Yes its outdated and might not work with recent kernels.
Packages
ekiga-dbg libopal3.6.1-dbg libpt2.6.3 libpt2.6.3-dbg installs just
fine here
I am using ekiga 3.2.1~git20090515 from Debian sid.
I am running Testing.
But the first thing is to try to install ptlib 2.6.3 and opal 3.6.3 from
unstable, maybe they fixed the issue! It seems to me that these
versions from unstable depend *only* on testing packages, cf.
http://release.debian.org/migration/testing.pl?package=opal;printalldeps=1
Try installing them from http://packages.debian.org/sid/libpt2.6.3 or
by temporarily allowing unstable in /etc/apt/sources.list...
I think I spent too little time when writing this e-mail, sorry.
Installing 2.6.3/3.6.3 does not mean that ekiga from debian will use
them, because the executable still asks for 2.6.1/3.6.1 (is that right?)
Until another better proposition arrive, I think the best is to install
ptlib/opal from unstable, and compile ekiga from git stable; and only if
the problem still occurs, use profiling.
--
Eugen
_______________________________________________
ekiga-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/ekiga-list
