Re: Softphones and arm builds with latest ccrtp, and exosip2 arm builds are broken

This is what I was getting:

 arm-linux-gcc -march=armv4 -mtune=xscale -DHAVE_CONFIG_H -I.
-I/mnt/oe/h3900/work/arm-linux/libeXosip2-2.2.3-r0/libeXosip2-2.2.3/src
-I.. -I/mnt/oe/h3900/work/arm-linux/libeXosip2-2.2.3-r0/libeXosip2-2.2.3
-I/mnt/oe/h3900/work/arm-linux/libeXosip2-2.2.3-r0/libeXosip2-2.2.3/include
-I/usr/include -I/mnt/oe/h3900/staging/arm-linux/include -Wall
-Wcast-align -Wchar-subscripts -Wformat -Winline -Wmissing-declarations
-Wmissing-prototypes -Wnested-externs -Wpointer-arith -DOSIP_MT
-pedantic -DENABLE_DEBUG -g -DENABLE_TRACE
-I/mnt/oe/h3900/staging/arm-linux/include -fexpensive-optimizations
-fomit-frame-pointer -frename-registers -pthread
-I/mnt/oe/h3900/staging/arm-linux/include -fexpensive-optimizations
-fomit-frame-pointer -frename-registers -MT udp.lo -MD -MP -MF
.deps/udp.Tpo -c udp.c  -fPIC -DPIC -o .libs/udp.o
| In file included from /usr/include/bits/socket.h:31,
|                  from /usr/include/sys/socket.h:35,
|                  from eXosip2.h:37,
|                  from udp.c:25:
| /usr/include/limits.h:124:3: warning: #include_next is a GCC extension
| In file included from /usr/include/limits.h:124,
|                  from /usr/include/bits/socket.h:31,
|                  from /usr/include/sys/socket.h:35,
|                  from eXosip2.h:37,
|                  from udp.c:25:
| /mnt/oe/h3900/staging/arm-linux/include/limits.h:124:3: warning:
#include_next is a GCC extension
| In file included from /usr/include/libio.h:32,
|                  from /usr/include/stdio.h:72,
|                  from eXosip2.h:43,
|                  from udp.c:25:
| /usr/include/_G_config.h:50: warning: invalid use of structure with
flexible array member
| In file included from
/mnt/oe/h3900/staging/arm-linux/include/osipparser2/osip_port.h:100,
|                  from
/mnt/oe/h3900/staging/arm-linux/include/osipparser2/osip_headers.h:25,
|                  from
/mnt/oe/h3900/staging/arm-linux/include/osipparser2/osip_message.h:25,
|                  from
/mnt/oe/h3900/staging/arm-linux/include/osipparser2/osip_parser.h:24,
|                  from
/mnt/oe/h3900/staging/arm-linux/include/osip2/osip.h:37,|
   from eXosip2.h:45,
|                  from udp.c:25:
| /usr/include/stdlib.h:514: warning: ISO C90 does not support `long long'
| udp.c: In function `eXosip_read_message':
| udp.c:1586: error: impossible constraint in `asm'
| udp.c:1632: error: impossible constraint in `asm'
| udp.c:1645: error: impossible constraint in `asm'
| udp.c:1713: error: impossible constraint in `asm'
| udp.c:1839: error: impossible constraint in `asm'
| make[2]: *** [udp.lo] Error 1
|

First and foremost, and I think your right, that there is some odd
configure/configuration issue going on, since I should NOT even be
getting -I/usr/include injected in there :).  The final error in udp.c
is actually on a fd_set macro, which is part of why I initially thought
it was so very strange.  But thinking further, it should not have any
/usr/include stuff....I think that, however that gets injected,
something there clashes with headers and things from the cross-compiler
environment, rather than something strange in the code base itself.

Aymeric Moizard wrote:
> 
> Hi David,
> 
> I'm compiling eXosip2 with no error on arm... Last time I tried was
> 2 weeks ago with 2.2.3 and CVS.
> 
> I guess you are only facing a minor issue with the configure script...
> 
> Aymeric
> 
> On Tue, 16 May 2006, David Sugar wrote:
> 
>> I have now also successfully built Twinkle without issues against
>> current CommonC++/ccrtp...
>>
>> David Sugar wrote:
>>> I have been able to successfully build sflphoned/sflphone-qt against the
>>> latest commoncpp2 (1.4.1) and ccrtp (1.4.0), and I will try to do the
>>> same with twinkle next.  I also have been able to successfully build
>>> ccrtp without difficulty on arm for ipaq for gpe/opie/qtopia.
>>>
>>> While I had no problem with libosip2, I have not been able to
>>> successfully cross-compile libeXosip2 for arm as yet, and I get many
>>> very odd bugs and errors in places that do not even make immediate sense
>>> to me.  This means probably neither sflphone nor twinkle will port
>>> successfully at this time, since they both also make use of exosip2
>>> code.
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Ccrtp-devel mailing list
>>> [email protected]
>>> http://lists.gnu.org/mailman/listinfo/ccrtp-devel
>>

_______________________________________________
Ccrtp-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/ccrtp-devel

begin:vcard
fn:David Sugar
n:Sugar;David
org:GNU Telephony
email;internet:[email protected]
tel;work:+1 201 215 2609
url:http://www.gnutelephony.org
version:2.1
end:vcard