unable to build with gcc 4 about libjingle

[GoogleCodeExporter]

See the thread
'http://groups.google.com/group/google-talk-open/browse_thread/thread/bf92d054c1
44f167'
for information about this issue (and source modifications needed to compile).

Original comment by [email protected] on 5 Mar 2007 at 3:48

[GoogleCodeExporter]

I checked out the source from SVN and modified the codes so that it can be 
built with
GCC 4.x and the latest oRTP library.but I don't know how to check back into the 
svn
repo,so i attached the modified source here.

Original comment by [email protected] on 19 Jul 2007 at 4:19

Attachments:

• libjingle.tar.gz

[GoogleCodeExporter]

Here are two patch files that you can use instead of over-writing all of your 
source
files with that tar.gz. To apply these patches, go under your libjingle-0.4.0
directory (so that you see "talk" as a subdir), and run:

patch -p1 < ortp.patch
patch -p1 < gcc4.patch

--
Matt

Original comment by mattwinter on 14 Nov 2007 at 6:25

Attachments:

• ortp.patch
• gcc4.patch

[GoogleCodeExporter]

gcc-4.3 is much more strict and previous patch is insufficient.

Here is a patch for version 0.4.0, which fixes all gcc-4.3 errors.

It is based on top of patches from issues 6 (ortp) and 11 (fileshare).

Original comment by [email protected] on 24 Jan 2008 at 6:37

Attachments:

• libjingle-0.4.0-gcc43.patch

[GoogleCodeExporter]

Fix for 0.3.0.

Original comment by [email protected] on 24 Jan 2008 at 6:46

Attachments:

• libjingle-0.3.0-gcc43.patch

[GoogleCodeExporter]

Warning: libjingle-0.4.0-gcc43.patch contains only fixes for build errors (plus 
one
missing #include "config.h"). But the code has also several problematic places
causing undefined behavior, which are not included:

- strict-aliasing problems in waveheader.h _readuint32 and _readuint16. 
Optimizer
without explicit -fno-strict-aliasing will probably compile the code 
incorrectly,
assuming that a and tmp1 are different memory locations (as they have different
types, which don't alias in strict-aliasing rules).

- several places where functions are declared as non-void but set no return 
value. It
results in an undefined behavior in gcc-4.3.

Related fix for Tapioca Project branch:
http://sourceforge.net/tracker/index.php?func=detail&aid=1879592&group_id=146406
&atid=765170

Original comment by [email protected] on 25 Jan 2008 at 11:49

[GoogleCodeExporter]

Patch svn version for gcc4.5.1 .

Original comment by [email protected] on 26 Aug 2010 at 2:26

Attachments:

• libjingle_gcc4.5.patch

[GoogleCodeExporter]

No longer applicable since new code release.

Original comment by [email protected] on 3 Nov 2010 at 7:18

• Changed state: Done