Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
Anything we do to the vanilla upstream is in the git repos here. Are you interested in improvements for open issues like the following? http://pkgs.fedoraproject.org/cgit/ptlib.git - Is the configuration file specification incomplete? https://sourceforge.net/tracker/?func=detailatid=989748aid=3603530group_id=204472 - Update candidates from autoheader? https://sourceforge.net/tracker/?func=detailatid=989748aid=3603551group_id=204472 http://pkgs.fedoraproject.org/cgit/opal.git Should the passed command parameters result into the same error messages for a configuration test? http://gcc.gnu.org/ml/gcc-help/2013-02/msg00032.html http://pkgs.fedoraproject.org/cgit/ekiga.git include adjustments https://bugzilla.gnome.org/review?bug=692964attachment=235032 https://bugzilla.gnome.org/review?bug=693109attachment=235125 Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
checking PTLIB has video... no This is the problem. Why does not ptlib have video support?! I get the following result if I reduce the command line parameters for the affected configuration test a bit. elfring@Sonne:~/Projekte/OpalVoip/OPAL/Probe LANG=C g++ -o Video1 -Wall -Wextra -Wstrict-aliasing -Wfloat-equal -Wno-comment -Wno-unused -Winit-self -Wno-missing-field-initializers -Wreorder -felide-constructors -fexceptions -fPIC -DP_64BIT -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -I/usr/local/include -I/usr/include/SDL -L/usr/local/lib64 -lpt_s -lrt -lsasl2 -lldap -llber -lldap_r -lssl -lcrypto -lexpat -llua -lSDL -lpthread -lodbc -lresolv -ldl Video1.cpp /tmp/ccc6uWN0.o: In function `main': Video1.cpp:(.text+0x17): undefined reference to `PVideoChannel::PVideoChannel()' Video1.cpp:(.text+0x2b): undefined reference to `PVideoChannel::~PVideoChannel()' /tmp/ccc6uWN0.o: In function `__static_initialization_and_destruction_0(int, int)': Video1.cpp:(.text+0x8c): undefined reference to `PFactoryLoader::PluginLoaderStartup_link()' Video1.cpp:(.text+0x97): undefined reference to `PPlugin_PVideoInputDevice_FakeVideo_link()' Video1.cpp:(.text+0xa2): undefined reference to `PPlugin_PVideoInputDevice_Application_link()' Video1.cpp:(.text+0xad): undefined reference to `PPlugin_PVideoInputDevice_FFMPEG_link()' Video1.cpp:(.text+0xb8): undefined reference to `PPlugin_PVideoInputDevice_YUVFile_link()' Video1.cpp:(.text+0xc3): undefined reference to `PPlugin_PVideoOutputDevice_SDL_link()' collect2: error: ld returned 1 exit status Would you like to share any more advices? Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On Tue, Feb 5, 2013 at 10:25 AM, Markus Elfring markus.elfr...@web.de wrote:
checking PTLIB has video... no
This is the problem. Why does not ptlib have video support?!
I get the following result if I reduce the command line parameters for the
affected configuration test a bit.
elfring@Sonne:~/Projekte/OpalVoip/OPAL/Probe LANG=C g++ -o Video1 -Wall
-Wextra
-Wstrict-aliasing -Wfloat-equal -Wno-comment -Wno-unused -Winit-self
-Wno-missing-field-initializers -Wreorder -felide-constructors -fexceptions
-fPIC -DP_64BIT -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -I/usr/local/include
-I/usr/include/SDL -L/usr/local/lib64 -lpt_s -lrt -lsasl2 -lldap -llber
-lldap_r
-lssl -lcrypto -lexpat -llua -lSDL -lpthread -lodbc -lresolv -ldl Video1.cpp
/tmp/ccc6uWN0.o: In function `main':
Video1.cpp:(.text+0x17): undefined reference to
`PVideoChannel::PVideoChannel()'
Video1.cpp:(.text+0x2b): undefined reference to
`PVideoChannel::~PVideoChannel()'
/tmp/ccc6uWN0.o: In function `__static_initialization_and_destruction_0(int,
int)':
Video1.cpp:(.text+0x8c): undefined reference to
`PFactoryLoader::PluginLoaderStartup_link()'
Video1.cpp:(.text+0x97): undefined reference to
`PPlugin_PVideoInputDevice_FakeVideo_link()'
Video1.cpp:(.text+0xa2): undefined reference to
`PPlugin_PVideoInputDevice_Application_link()'
Video1.cpp:(.text+0xad): undefined reference to
`PPlugin_PVideoInputDevice_FFMPEG_link()'
Video1.cpp:(.text+0xb8): undefined reference to
`PPlugin_PVideoInputDevice_YUVFile_link()'
Video1.cpp:(.text+0xc3): undefined reference to
`PPlugin_PVideoOutputDevice_SDL_link()'
collect2: error: ld returned 1 exit status
Would you like to share any more advices?
I've seen issues with building ptlib/opal in the past if you don't
have all the right dependencies in place. The ptlib/opal/ekiga combo
for ekiga 4.0 build just fine with gcc 4.7.x as that what Fedora 17/18
use.
The dependencies (Fedora naming so will need adjusting for other
distros) I have for ptlib are:
BuildRequires: pkgconfig, expat-devel, flex, bison
BuildRequires: alsa-lib-devel, libv4l-devel
BuildRequires: openldap-devel, SDL-devel, openssl-devel
BuildRequires: boost-devel, pulseaudio-libs-devel
The configure I use is:
%configure --prefix=%{_prefix} --disable-static --enable-plugins
--disable-oss --enable-v4l2 --disable-avc --disable-v4l --enable-pulse
I disable the old v4l and just use v4l2 as it's been dropped from newer kernels.
Deps for opal are:
BuildRequires: ptlib-devel = 2.10.9
BuildRequires: openldap-devel
BuildRequires: openssl-devel
BuildRequires: libtheora-devel
BuildRequires: speex-devel
BuildRequires: SDL-devel
BuildRequires: expat-devel
and the configure line I use is:
%configure --disable-silk
Regards,
Peter
Peter
___
ekiga-devel-list mailing list
ekiga-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
I've seen issues with building ptlib/opal in the past if you don't have all the right dependencies in place. Thanks for your feedback. Do you maintain any patches to circumvent or fix changes in application programming interfaces like it happened with the software library ffmpeg? Have you got any hints where reference patterns like _link and __static_initialization_and_destruction_0 do come from? Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On Tue, Feb 5, 2013 at 12:13 PM, Markus Elfring markus.elfr...@web.de wrote: I've seen issues with building ptlib/opal in the past if you don't have all the right dependencies in place. Thanks for your feedback. Do you maintain any patches to circumvent or fix changes in application programming interfaces like it happened with the software library ffmpeg? Fedora doesn't use any proprietary codecs so the ffmpeg stuff isn't built and in fact we strip some of the codecs out of opal because of their non-free status so ffmpeg is not a problem I ever have to deal with. We explicitly remove the directories plugins/video/H.263-1998/ plugins/video/H.264/ plugins/video/MPEG4-ffmpeg/ before we upload the tar file into Fedora's build infra. I once asked upstream whether we could split them out into a non-free tar file release or even ship them separately but disappointingly got hailed down. Anything we do to the vanilla upstream is in the git repos here. http://pkgs.fedoraproject.org/cgit/ptlib.git http://pkgs.fedoraproject.org/cgit/opal.git http://pkgs.fedoraproject.org/cgit/ekiga.git Have you got any hints where reference patterns like _link and __static_initialization_and_destruction_0 do come from? Sounds like linker related bits. What distro are you using? I suggest getting it building with out ffmpeg first in your environment so you know the basics work and then add ffmpeg to a configuration that you know is working. Peter ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
What distro are you using? openSUSE (various releases over the years and Tumbleweed now) I suggest getting it building with out ffmpeg first in your environment so you know the basics work and then add ffmpeg to a configuration that you know is working. I hope that this software component can also be eventually excluded by corresponding configuration options (command line parameters). Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On 5 Feb 2013 12:36, Markus Elfring markus.elfr...@web.de wrote: What distro are you using? openSUSE (various releases over the years and Tumbleweed now) I suggest getting it building with out ffmpeg first in your environment so you know the basics work and then add ffmpeg to a configuration that you know is working. I hope that this software component can also be eventually excluded by corresponding configuration options (command line parameters). You can exclude the building of it already with configure. Fedora policy explicitly excludes distribution of that stuff including the source and hence we remove it before uploading for build. Peter ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On 04/02/13 14:18, Markus Elfring wrote: Now I stumble on the next open issues that are shown by my compiler g++ 4.7.2 for the current application development version. How do you think about the following information? Excerpt from build log: ... make[3]: Entering directory `/home/elfring/Projekte/Gnome/Ekiga/lokal/src' /bin/sh ../libtool --tag=CXX --mode=link g++ -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14 -I/usr/include/harfbuzz -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DP_64BIT -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -fexceptions -I/usr/local/include -I/usr/local/include/opal -I/usr/include/SDL -DP_64BIT -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -fexceptions -I/usr/local/include -I/usr/include/SDL -I/usr/include -I/usr/include/libxml2 -g -O2 -Wall -Wextra -Winit-self -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal -Wshadow -lX11 -o ekiga assistant.o main.o main_window.o ekiga.o dbus.o ../lib/libekiga.la -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lglib-2.0 -Wl,--export-dynamic -pthread -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lrt -lglib-2.0 -ldbus-glib-1 -ldbus-1 -lgobject-2.0 -lglib-2.0 -L/usr/local/lib64 -lopal -lpt -lspeexdsp -L/usr/local/lib64 -lpt -L/usr/lib64 -lboost_signals-mt -lxml2 -lresolv ... linking .libs/ekiga (g++) ../lib/.libs/libekiga.so: undefined reference to `PPlugin_PVideoInputDevice_Application_link()' collect2: error: ld returned 1 exit status ... Would you like to share any ideas or hints for this message? The problem, Markus, is that strange things happen on your system. To speed up error discovery, would you allow me to have access to your machine through a solution such as vinagre/vino? You will see everything I do, no need to worry... -- Eugen ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
checking PTLIB has video... no This is the problem. Why does not ptlib have video support?! I wonder also that this configuration check fails. Excerpt from ~/Projekte/OpalVoip/OPAL/3.10.9/config.log: ... /usr/local/lib64/libpt_s.a(vsdl.o): In function `_GLOBAL__sub_I_vsdl.cxx': vsdl.cxx:(.text.startup+0x42): undefined reference to `PPlugin_PVideoInputDevice_Application_link()' /usr/local/lib64/libpt_s.a(vfakeio.o): In function `_GLOBAL__sub_I_vfakeio.cxx': vfakeio.cxx:(.text.startup+0x42): undefined reference to `PPlugin_PVideoInputDevice_Application_link()' ... Do I stumble on a broken link dependency here? Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
If you want to do development work, then you can try v12 and inform us about the patches you use so that we can commit them when we switch to v12 (in very few months). It seems there will be some updates needed for header file paths from Eridani and Lacaille. https://sourceforge.net/mailarchive/message.php?msg_id=30403346 Would you like to integrate any additional checks into your configuration scripts and source files? Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
Now I stumble on the next open issues ... I might have got a clue for a few compilation error messages like 'PVideoInputDevice' has not been declared. I wonder why some include statements were commented out in the main header file for the component PTlib. http://opalvoip.svn.sourceforge.net/viewvc/opalvoip/ptlib/tags/v2_10_9/include/ptlib.h?revision=28589view=markup It seems that their exclusion (by default) can not be avoided by a corresponding build configuration. Can it be that companion header files like video.h need to be explicitly referenced at other source code places? Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On 02/02/13 19:28, Markus Elfring wrote: Now I stumble on the next open issues ... I might have got a clue for a few compilation error messages like 'PVideoInputDevice' has not been declared. I wonder why some include statements were commented out in the main header file for the component PTlib. http://opalvoip.svn.sourceforge.net/viewvc/opalvoip/ptlib/tags/v2_10_9/include/ptlib.h?revision=28589view=markup It seems that their exclusion (by default) can not be avoided by a corresponding build configuration. Can it be that companion header files like video.h need to be explicitly referenced at other source code places? I do not understand what you say... I have just tested: compilation works here with your version/commit of ekiga. So the problem should be a disabled option in ptlib which interacts with ekiga. What command line have you used for building ptlib? Could you send me the file make/ptbuildopts.mak from ptlib directory where you compiled? PS Please do not remove lines from e-mail when replying. -- Eugen ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
... a known-compatible version : just let opal use those sources, and things will go smoothly. Luyten and Eridani like to surprise me on my system so far ... :-( Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On 01/02/13 08:59, Julien Puydt wrote: Le 01/02/2013 08:56, Markus Elfring a écrit : Those symbols are supposed to come from ffmpeg. I know that ... ;-) https://sourceforge.net/tracker/?func=detailatid=989748aid=3602510group_id=204472 When I can not change the reused source files directly, I'll have to extend/adapt my build environment, won't I? Is another developers game dependency hell going on here? Which corresponding source file versions should I try to reactivate? ffmpeg keeps on making incompatible changes to their api ; that is the reason why opal's sources contain a known-compatible version : just let opal use those sources, and things will go smoothly. Opal does not have sources of ffmpeg, as far as I know, but only some #define to make it compile with several versions of ffmpeg. The simplest solution I see is that you configure with --disable-h264 --disable-h263, does this fit your needs? A better solution is to backport the recent relevant changes from trunk to v10. -- Eugen ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On 01/02/13 09:06, Markus Elfring wrote: ... a known-compatible version : just let opal use those sources, and things will go smoothly. Luyten and Eridani like to surprise me on my system so far ... :-( There is only one surprise here :), because ekiga is not yet made to work with v12. -- Eugen ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On 01/02/13 14:20, Markus Elfring wrote: The simplest solution I see is that you configure with --disable-h264 --disable-h263, does this fit your needs? Probably, yes - if the desired software exclusion would work here. elfring@Sonne:~/Projekte/OpalVoip/OPAL/3.10.9 ./configure --disable-h263 --disable-h264 ... === Plugin configuration == ... H.263/H.263+ : yes (ffmpeg) H.264 : yes (GPL x264) ... Ah! Those plugins cannot be disabled, and no error is shown because of inexistent options... Then just remove plugins/video/H.263-1998 etc. directories and rebuild, this works for sure. -- Eugen ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
Then just remove plugins/video/H.263-1998 etc. directories and rebuild, this works for sure. Unfortunately not. The current configuration script insists on the existence of the file Makefile.in. Excerpt from the build log: ... make[3]: Entering directory `/home/elfring/Projekte/OpalVoip/OPAL/3.10.9/plugins/video/H.263-1998' make[3]: *** No rule to make target `/home/elfring/Projekte/OpalVoip/OPAL/3.10.9/plugins/../lib_linux_x86_64/plugins/h263_ffmpeg/h263-1998.o', needed by `/home/elfring/Projekte/OpalVoip/OPAL/3.10.9/plugins/../lib_linux_x86_64/plugins/h263_ffmpeg/h263_ffmpeg_ptplugin.so'. ... Does the build specification configure.ac need any updates for the support of plug-in exclusion here? Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
Could you try configure with --disable-libavcodec ?
Yes ...
(I wonder that this option was not listed by the command ./configure --help.)
A corresponding result looks promising for my situation:
...
=== Plugin configuration ==
...
H.261 : yes (vic)
H.263/H.263+ : no (ffmpeg)
H.264 : no
THEORA : yes
MPEG4 Part 2 : no
...
I have build and installed this configuration variant for the software library
OPAL 3.10.9 successfully. - Thanks for your support.
Now I stumble on the next open issues that are shown by my compiler g++ 4.7.2
for the current application development version.
Excerpt from the build log:
...
make[3]: Entering directory `/home/elfring/Projekte/Gnome/Ekiga/lokal/lib'
...
In file included from ../lib/engine/components/opal/opal-call-manager.h:55:0,
from ../lib/engine/components/opal/opal-call-manager.cpp:41:
../lib/engine/components/opal/opal-call.h: In member function
'PSafePtrOpalConnection Opal::Call::get_remote_connection()':
../lib/engine/components/opal/opal-call.h:211:42: error: 'OpalPCSSConnection'
was not declared in this scope
../lib/engine/components/opal/opal-call.h:211:71: error: no matching function
for call to 'PSafePtrCast(PSafePtrOpalConnection)'
...
In file included from ../lib/engine/components/opal/opal-call-manager.h:55:0,
from ../lib/engine/components/opal/opal-call-manager.cpp:41:
../lib/engine/components/opal/opal-call.h:211:71: error: template argument 2 is
invalid
In file included from ../lib/engine/components/opal/opal-call-manager.cpp:41:0:
../lib/engine/components/opal/opal-call-manager.h: At global scope:
../lib/engine/components/opal/opal-call-manager.h:191:46: error:
'PVideoOutputDevice' has not been declared
../lib/engine/components/opal/opal-call-manager.cpp: In constructor
'Opal::CallManager::CallManager(Ekiga::ServiceCore)':
../lib/engine/components/opal/opal-call-manager.cpp:124:34: error:
'SetAutoStartTransmitVideo' was not declared in this scope
../lib/engine/components/opal/opal-call-manager.cpp:125:33: error:
'SetAutoStartReceiveVideo' was not declared in this scope
../lib/engine/components/opal/opal-call-manager.cpp:139:3: error: 'PVideoDevice'
has not been declared
../lib/engine/components/opal/opal-call-manager.cpp:139:26: error: expected ';'
before 'video'
../lib/engine/components/opal/opal-call-manager.cpp:140:3: error: 'video' was
not declared in this scope
../lib/engine/components/opal/opal-call-manager.cpp:141:30: error:
'SetVideoOutputDevice' was not declared in this scope
../lib/engine/components/opal/opal-call-manager.cpp:143:32: error:
'GetVideoOutputDevice' was not declared in this scope
../lib/engine/components/opal/opal-call-manager.cpp:145:31: error:
'SetVideoPreviewDevice' was not declared in this scope
../lib/engine/components/opal/opal-call-manager.cpp:147:31: error:
'GetVideoInputDevice' was not declared in this scope
../lib/engine/components/opal/opal-call-manager.cpp:149:29: error:
'SetVideoInputDevice' was not declared in this scope
../lib/engine/components/opal/opal-call-manager.cpp: In member function 'virtual
void Opal::CallManager::set_codecs(Ekiga::CodecList)':
../lib/engine/components/opal/opal-call-manager.cpp:450:23: error:
'OpalTranscoder' has not been declared
../lib/engine/components/opal/opal-call-manager.cpp: In member function 'void
Opal::CallManager::set_video_options(const Opal::CallManager::VideoOptions)':
../lib/engine/components/opal/opal-call-manager.cpp:590:38: error:
'OpalVideoFormat' has not been declared
...
make[3]: *** [opal-main.lo] Error 1
CXX opal-audio.lo
CXX opal-videoinput.lo
In file included from ../lib/engine/components/opal/opal-videoinput.cpp:39:0:
../lib/engine/components/opal/opal-videoinput.h:50:1: error: expected class-name
before '{' token
../lib/engine/components/opal/opal-videoinput.h:135:32: error: 'VideoFormat' has
not been declared
...
../lib/engine/components/opal/h323-endpoint.cpp: In member function 'void
Opal::H323::EndPoint::on_transfer(std::string)':
../lib/engine/components/opal/h323-endpoint.cpp:459:10: error: ISO C++ forbids
declaration of 'type name' with no type [-fpermissive]
../lib/engine/components/opal/h323-endpoint.cpp:459:10: error: expected ''
before 'OpalPCSSConnection'
../lib/engine/components/opal/h323-endpoint.cpp:459:10: error: expected '('
before 'OpalPCSSConnection'
../lib/engine/components/opal/h323-endpoint.cpp:459:10: error:
'OpalPCSSConnection' was not declared in this scope
../lib/engine/components/opal/h323-endpoint.cpp:459:10: error: expected
primary-expression before '' token
../lib/engine/components/opal/h323-endpoint.cpp:460:7: error: expected ')'
before 'connection'
...
Regards,
Markus
___
ekiga-devel-list mailing list
ekiga-devel-list@gnome.org
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On 01/02/13 18:00, Markus Elfring wrote: (I wonder that this option was not listed by the command ./configure --help.) Because it is provided by plugins/configure. To see it you need --help=recursive... -- Eugen ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On 01/02/13 18:00, Markus Elfring wrote: Could you try configure with --disable-libavcodec ? Now I stumble on the next open issues that are shown by my compiler g++ 4.7.2 for the current application development version. Excerpt from the build log: ... make[3]: Entering directory `/home/elfring/Projekte/Gnome/Ekiga/lokal/lib' ... In file included from ../lib/engine/components/opal/opal-call-manager.h:55:0, from ../lib/engine/components/opal/opal-call-manager.cpp:41: ../lib/engine/components/opal/opal-call.h: In member function 'PSafePtrOpalConnection Opal::Call::get_remote_connection()': ../lib/engine/components/opal/opal-call.h:211:42: error: 'OpalPCSSConnection' was not declared in this scope ../lib/engine/components/opal/opal-call.h:211:71: error: no matching function for call to 'PSafePtrCast(PSafePtrOpalConnection)' ... What ekiga do you use? v4_0, master which git commit etc. -- Eugen ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
What ekiga do you use? v4_0, master which git commit etc. I would like to try out if the master version is already usable at the moment. http://git.gnome.org/browse/ekiga/commit/?id=8bff99914b7d8bc43a64f19c803c9c579ce00c01 Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
ekiga 4 and associated dependencies builds fine on Fedora 17/18 and rawhide. You might want to have a look at our specs. To which specific file do you refer to here? https://admin.fedoraproject.org/pkgdb/applications/Ekiga%20Softphone?_csrf_token=ef3acbb6c94fb349038b447546e9f97b42f6dfb1 Which compiler versions do you try out for the build of the current application? http://rpmfind.net/linux/RPM/fedora/devel/rawhide/x86_64/e/ekiga-4.0.0-2.fc19.x86_64.html Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On 30/01/13 22:22, Markus Elfring wrote: If your kdevelop uses gcc 4.4.1, then this could easily be explained, since recent gcc have become stricter and stricter about the C syntax. No - This integrated development environment calls just the compiler version (g++ 4.7.1) that is provided by the openSUSE distribution here. I do not know why this error then. To debug this we need configure.log in both cases. If you need ekiga as a user, then use v10. I can refer also to this version level if I pass appropriate values for parameters like PTLIB_CFLAGS and OPAL_CFLAGS to the command configure. But I suppose all these problems arrive because you have two versions of ptlib/opal installed, more specifically their development files. Why do not want to remove the development files (devel package?) of v10 if you wish to use v12, or vice-versa? Do you need both devel files simultaneously? -- Eugen ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
I do not know why this error then. Which compiler versions do you try out in your builds at the moment? Do you need both devel files simultaneously? I dared to try out newer versions. It might be interesting to compare the available releases for the stable software libraries. Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
Why do not want to remove the development files (devel package?) of v10 if you wish to use v12, or vice-versa? The current application has also got specific requirements that can not be resolved by openSUSE 12.2 at the moment. elfring@Sonne:~/Projekte/Gnome/Ekiga/lokal ./configure ... configure: error: Package requirements (ptlib = 2.10.9) were not met: Requested 'ptlib = 2.10.9' but version of ptlib is 2.10.5 ... So I try to generate newer versions from the corresponding source files ... Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On 31/01/13 10:29, Markus Elfring wrote: Why do not want to remove the development files (devel package?) of v10 if you wish to use v12, or vice-versa? The current application has also got specific requirements that can not be resolved by openSUSE 12.2 at the moment. elfring@Sonne:~/Projekte/Gnome/Ekiga/lokal ./configure ... configure: error: Package requirements (ptlib= 2.10.9) were not met: Requested 'ptlib= 2.10.9' but version of ptlib is 2.10.5 ... So I try to generate newer versions from the corresponding source files ... Then remove devel package of 2.10.5 and use 2.10.9 for development, without using 2.12.x. -- Eugen ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
... use 2.10.9 for development, without using 2.12.x. I have begun to try this approach, too. But I get another surprise. elfring@Sonne:~/Projekte/OpalVoip/OPAL/3.10.9 ./configure ... ⇒ Excerpt from the build log: ... make[3]: Entering directory `/home/elfring/Projekte/OpalVoip/OPAL/3.10.9/plugins/video/H.263-1998' ... h263-1998.cxx: In member function ‘virtual void H263_Base_EncoderContext::SetOption(const char*, const char*)’: h263-1998.cxx:320:27: error: ‘CODEC_FLAG_H263P_UMV’ was not declared in this scope h263-1998.cxx:322:28: error: ‘CODEC_FLAG_H263P_UMV’ was not declared in this scope h263-1998.cxx:363:27: error: ‘CODEC_FLAG_H263P_SLICE_STRUCT’ was not declared in this scope h263-1998.cxx:365:28: error: ‘CODEC_FLAG_H263P_SLICE_STRUCT’ was not declared in this scope h263-1998.cxx:373:27: error: ‘CODEC_FLAG_H263P_AIV’ was not declared in this scope h263-1998.cxx:375:28: error: ‘CODEC_FLAG_H263P_AIV’ was not declared in this scope h263-1998.cxx: In member function ‘bool H263_Base_EncoderContext::OpenCodec()’: h263-1998.cxx:455:3: error: ‘CODEC_FLAG_H263P_UMV’ was not declared in this scope h263-1998.cxx:456:3: error: ‘CODEC_FLAG_OBMC’ was not declared in this scope h263-1998.cxx:458:3: error: ‘CODEC_FLAG_H263P_SLICE_STRUCT’ was not declared in this scope h263-1998.cxx:460:3: error: ‘CODEC_FLAG_H263P_AIV’ was not declared in this scope h263-1998.cxx: In member function ‘virtual bool H263_Base_EncoderContext::EncodeFrames(const BYTE*, unsigned int, BYTE*, unsigned int, unsigned int)’: h263-1998.cxx:524:72: error: ‘FF_I_TYPE’ was not declared in this scope h263-1998.cxx: In member function ‘virtual bool H263_RFC2190_EncoderContext::Init()’: h263-1998.cxx:606:24: error: ‘CODEC_FLAG_H263P_UMV’ was not declared in this scope h263-1998.cxx:611:24: error: ‘CODEC_FLAG_H263P_AIV’ was not declared in this scope h263-1998.cxx:612:24: error: ‘CODEC_FLAG_H263P_SLICE_STRUCT’ was not declared in this scope make[3]: *** [/home/elfring/Projekte/OpalVoip/OPAL/3.10.9/plugins/../lib_linux_x86_64/plugins/h263_ffmpeg/h263-1998.o] Error 1 ... Do I need to add any old header files to my build environment so that these preprocessor symbols can be resolved? Are there any chances to complete the version information in the involved configuration checks? Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
Those symbols are supposed to come from ffmpeg. I know that ... ;-) https://sourceforge.net/tracker/?func=detailatid=989748aid=3602510group_id=204472 When I can not change the reused source files directly, I'll have to extend/adapt my build environment, won't I? Is another developers game dependency hell going on here? Which corresponding source file versions should I try to reactivate? Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
Le 01/02/2013 08:56, Markus Elfring a écrit : Those symbols are supposed to come from ffmpeg. I know that ... ;-) https://sourceforge.net/tracker/?func=detailatid=989748aid=3602510group_id=204472 When I can not change the reused source files directly, I'll have to extend/adapt my build environment, won't I? Is another developers game dependency hell going on here? Which corresponding source file versions should I try to reactivate? ffmpeg keeps on making incompatible changes to their api ; that is the reason why opal's sources contain a known-compatible version : just let opal use those sources, and things will go smoothly. Snark ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
Where did you download opal and ptlib from? I have got these software libraries from the official repositories. What version? | Subversion | openSUSE --++- ptlib | 2.12 | 2.10.5-2.1.2 opal | 3.12 | 3.10.5-2.1.2 See also update candidates for a few corresponding plug-ins: https://sourceforge.net/tracker/?func=detailatid=989748aid=3600658group_id=204472 https://sourceforge.net/tracker/?func=detailatid=989748aid=3602450group_id=204472 https://sourceforge.net/tracker/?func=detailatid=989748aid=3602510group_id=204472 Regards, Markus ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On 30/01/13 09:44, Markus Elfring wrote: Where did you download opal and ptlib from? I have got these software libraries from the official repositories. What version? | Subversion | openSUSE --++- ptlib | 2.12 | 2.10.5-2.1.2 opal | 3.12 | 3.10.5-2.1.2 The problem is that ekiga is tested with 2.10/3.10 versions, as shown at http://wiki.ekiga.org/index.php/Download_Ekiga_sources. It has not been tested with .12 versions, and there are API breakages, as you noticed. Do you have a strong reason to use .12 versions? I suggest you to use .10 version. See also update candidates for a few corresponding plug-ins: https://sourceforge.net/tracker/?func=detailatid=989748aid=3600658group_id=204472 https://sourceforge.net/tracker/?func=detailatid=989748aid=3602450group_id=204472 https://sourceforge.net/tracker/?func=detailatid=989748aid=3602510group_id=204472 Yes, I have seen them, thank you. -- Eugen ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
If your kdevelop uses gcc 4.4.1, then this could easily be explained, since
recent gcc have become stricter and stricter about the C syntax.
No - This integrated development environment calls just the compiler version
(g++ 4.7.1) that is provided by the openSUSE distribution here.
If you need ekiga as a user, then use v10.
I can refer also to this version level if I pass appropriate values for
parameters like PTLIB_CFLAGS and OPAL_CFLAGS to the command configure. But
I still wonder about results like the following.
...
make[3]: Entering directory `/home/elfring/Projekte/Gnome/Ekiga/lokal/lib'
CXX videoinput-manager-ptlib.lo
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual bool GMVideoInputManager_ptlib::open(unsigned int, unsigned int,
unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:152:17: error:
'class PVideoInputDevice' has no member named 'GetParameters'
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual void GMVideoInputManager_ptlib::set_colour(unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:201:19: error:
'class PVideoInputDevice' has no member named 'SetColour'
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual void GMVideoInputManager_ptlib::set_brightness(unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:208:19: error:
'class PVideoInputDevice' has no member named 'SetBrightness'
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual void GMVideoInputManager_ptlib::set_whiteness(unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:215:19: error:
'class PVideoInputDevice' has no member named 'SetWhiteness'
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual void GMVideoInputManager_ptlib::set_contrast(unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:222:19: error:
'class PVideoInputDevice' has no member named 'SetContrast'
make[3]: *** [videoinput-manager-ptlib.lo] Error 1
CXX opal-call-manager.lo
../lib/engine/components/opal/opal-call-manager.cpp: In member function 'virtual
void Opal::CallManager::set_maximum_jitter(unsigned int)':
../lib/engine/components/opal/opal-call-manager.cpp:230:28: error: no matching
function for call to 'max(unsigned int, int)'
../lib/engine/components/opal/opal-call-manager.cpp:230:28: note: candidates
are:
In file included from /usr/include/c++/4.7/algorithm:62:0,
from ../lib/engine/components/opal/opal-call-manager.cpp:38:
/usr/include/c++/4.7/bits/stl_algobase.h:210:5: note: templateclass _Tp const
_Tp std::max(const _Tp, const _Tp)
/usr/include/c++/4.7/bits/stl_algobase.h:210:5: note: template argument
deduction/substitution failed:
../lib/engine/components/opal/opal-call-manager.cpp:230:28: note: deduced
conflicting types for parameter 'const _Tp' ('unsigned int' and 'int')
...
../lib/engine/components/opal/opal-call-manager.cpp: In member function 'void
Opal::CallManager::set_video_options(const Opal::CallManager::VideoOptions)':
../lib/engine/components/opal/opal-call-manager.cpp:600:40: error:
'RateControlPeriodOption' is not a member of 'OpalVideoFormat'
In file included from /usr/local/include/ptclib/threadpool.h:44:0,
from /usr/local/include/ptlib/timer.h:43,
from /usr/local/include/ptlib.h:66,
from ../lib/engine/components/opal/opal-call-manager.h:45,
from ../lib/engine/components/opal/opal-call-manager.cpp:41:
/usr/local/include/ptlib/safecoll.h: In instantiation of 'PSafePtrT,
BaseClass::operator T*() const [with T = OpalMediaPatch; BaseClass =
PSafePtrMultiThreaded]':
/usr/include/opal/opal/mediastrm.h:384:48: required from here
/usr/local/include/ptlib/safecoll.h:900:80: error: cannot dynamic_cast '((const
PSafePtrOpalMediaPatch, PSafePtrMultiThreaded*)this)-PSafePtrOpalMediaPatch,
PSafePtrMultiThreaded::anonymous.PSafePtrMultiThreaded::anonymous.PSafePtrBase::currentObject'
(of type 'class PSafeObject* const') to type 'class OpalMediaPatch*' (target is
not pointer or reference to complete type)
In file included from /usr/include/opal/opal/mediafmt.h:47:0,
from /usr/include/opal/opal/mediastrm.h:43,
from /usr/include/opal/im/im.h:71,
from /usr/include/opal/opal/pres_ent.h:43,
from /usr/include/opal/opal/manager.h:41,
from /usr/include/opal/opal/endpoint.h:41,
from /usr/include/opal/opal/rtpep.h:38,
from /usr/include/opal/h323/h323ep.h:45,
from /usr/include/opal/h323/h323.h:39,
from ../lib/engine/components/opal/opal-call-manager.h:47,
from ../lib/engine/components/opal/opal-call-manager.cpp:41:
...
Regards,
Markus
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
Le 30/01/2013 22:22, Markus Elfring a écrit : If your kdevelop uses gcc 4.4.1, then this could easily be explained, since recent gcc have become stricter and stricter about the C syntax. No - This integrated development environment calls just the compiler version (g++ 4.7.1) that is provided by the openSUSE distribution here. If you need ekiga as a user, then use v10. I can refer also to this version level if I pass appropriate values for parameters like PTLIB_CFLAGS and OPAL_CFLAGS to the command configure. But I still wonder about results like the following. Why do you wonder? Obviously the code isn't supposed to be compatible with v12, and the configure script has a bug in that it doesn't detect this problem. Snark ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
[Ekiga-devel-list] Challenges for generation of Ekiga 4.x
Hello!
I try to generate your current software on my openSUSE Tumbleweed system.
http://git.gnome.org/browse/ekiga/commit/?id=21f16237823bb0f2ac8af644e7557bc38963bfc9
I stumble on the following open issues.
1. The header file opal/pcss.h is referenced by your header file
pcss-endpoint.h. But I get difficulties because it was installed into the
directory /usr/include/opal/opal/.
Can an additional subdirectory be configured?
2. Build failures
/home/elfring/Projekte/Gnome/Ekiga/lokal/ make -j4
...
make[3]: Entering directory `/home/elfring/Projekte/Gnome/Ekiga/lokal/lib'
...
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual bool GMVideoInputManager_ptlib::open(unsigned int, unsigned int,
unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:152:17: error:
'class PVideoInputDevice' has no member named 'GetParameters'
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual void GMVideoInputManager_ptlib::set_colour(unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:201:19: error:
'class PVideoInputDevice' has no member named 'SetColour'
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual void GMVideoInputManager_ptlib::set_brightness(unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:208:19: error:
'class PVideoInputDevice' has no member named 'SetBrightness'
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual void GMVideoInputManager_ptlib::set_whiteness(unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:215:19: error:
'class PVideoInputDevice' has no member named 'SetWhiteness'
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp: In member function
'virtual void GMVideoInputManager_ptlib::set_contrast(unsigned int)':
../lib/engine/components/ptlib/videoinput-manager-ptlib.cpp:222:19: error:
'class PVideoInputDevice' has no member named 'SetContrast'
make[3]: *** [videoinput-manager-ptlib.lo] Error 1
make[3]: *** Waiting for unfinished jobs
In file included from ../lib/engine/components/opal/opal-call-manager.h:51:0,
from ../lib/engine/components/opal/opal-call-manager.cpp:41:
../lib/engine/components/opal/opal-call.h:184:68: error: 'RTP_Session' does not
name a type
../lib/engine/components/opal/opal-call.h:184:82: error: ISO C++ forbids
declaration of 'session' with no type [-fpermissive]
../lib/engine/components/opal/opal-call.h: In member function
'PSafePtrOpalConnection Opal::Call::get_remote_connection()':
../lib/engine/components/opal/opal-call.h:211:42: error: 'OpalPCSSConnection'
was not declared in this scope
../lib/engine/components/opal/opal-call.h:211:71: error: no matching function
for call to 'PSafePtrCast(PSafePtrOpalConnection)'
../lib/engine/components/opal/opal-call.h:211:71: note: candidate is:
In file included from /usr/local/include/ptclib/threadpool.h:44:0,
from /usr/local/include/ptlib/timer.h:43,
from /usr/local/include/ptlib.h:66,
from ../lib/engine/components/opal/opal-call-manager.h:45,
from ../lib/engine/components/opal/opal-call-manager.cpp:41:
/usr/local/include/ptlib/safecoll.h:959:19: note: templateclass Base, class
Derived PSafePtrDerived PSafePtrCast(const PSafePtrBase)
/usr/local/include/ptlib/safecoll.h:959:19: note: template argument
deduction/substitution failed:
In file included from ../lib/engine/components/opal/opal-call-manager.h:51:0,
from ../lib/engine/components/opal/opal-call-manager.cpp:41:
../lib/engine/components/opal/opal-call.h:211:71: error: template argument 2 is
invalid
../lib/engine/components/opal/opal-call-manager.cpp: In member function 'virtual
void Opal::CallManager::set_maximum_jitter(unsigned int)':
../lib/engine/components/opal/opal-call-manager.cpp:230:28: error: no matching
function for call to 'max(unsigned int, int)'
../lib/engine/components/opal/opal-call-manager.cpp:230:28: note: candidates
are:
In file included from /usr/include/c++/4.7/algorithm:62:0,
from ../lib/engine/components/opal/opal-call-manager.cpp:38:
/usr/include/c++/4.7/bits/stl_algobase.h:210:5: note: templateclass _Tp const
_Tp std::max(const _Tp, const _Tp)
/usr/include/c++/4.7/bits/stl_algobase.h:210:5: note: template argument
deduction/substitution failed:
../lib/engine/components/opal/opal-call-manager.cpp:230:28: note: deduced
conflicting types for parameter 'const _Tp' ('unsigned int' and 'int')
In file included from /usr/include/c++/4.7/algorithm:62:0,
from ../lib/engine/components/opal/opal-call-manager.cpp:38:
/usr/include/c++/4.7/bits/stl_algobase.h:254:5: note: templateclass _Tp, class
_Compare const _Tp std::max(const _Tp, const _Tp, _Compare)
/usr/include/c++/4.7/bits/stl_algobase.h:254:5: note: template argument
deduction/substitution failed:
Re: [Ekiga-devel-list] Challenges for generation of Ekiga 4.x
On Tue, Jan 29, 2013 at 9:30 PM, Markus Elfring markus.elfr...@web.de wrote: Hello! I try to generate your current software on my openSUSE Tumbleweed system. http://git.gnome.org/browse/ekiga/commit/?id=21f16237823bb0f2ac8af644e7557bc38963bfc9 I stumble on the following open issues. 1. The header file opal/pcss.h is referenced by your header file pcss-endpoint.h. But I get difficulties because it was installed into the directory /usr/include/opal/opal/. Can an additional subdirectory be configured? 2. Build failures ekiga 4 and associated dependencies builds fine on Fedora 17/18 and rawhide. You might want to have a look at our specs. Peter ___ ekiga-devel-list mailing list ekiga-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-devel-list
