[sr-dev] Kamailio master build failing on Raspberry Pi (raspbian)
Daniel-Constantin Mierla
miconda at gmail.com
Tue Sep 10 21:13:21 CEST 2013
You can commit the change, I am not aware of arm6 with smp, but if shows
up, then we will fix it.
Cheers,
Daniel
On Tue, Sep 10, 2013 at 6:59 PM, Peter Dunkley <
peter.dunkley at crocodilertc.net> wrote:
> Looking in Makefile.defs I noticed that the "arm" architecture has
> "-DNOSMP" added to C_DEFS but the "arm6" architecture does not.
>
> Under Fedora (at least when I was using it) the Raspberry Pi uses the
> "armv5tel" architecture (the old "arm") even though the Raspberry Pi is
> natively "arm6". Raspbian supports the "arm6" architecture.
>
> So it looks like (for Raspberry Pi use) "-DNOSMP" needs to be set for the
> "arm6" architecture.
>
> Does anyone have a problem with me doing this? Does anyone know of, or
> forsee, an "arm6" device with SMP support?
>
> Regards,
>
> Peter
>
>
> On 10 September 2013 17:50, Peter Dunkley <peter.dunkley at crocodilertc.net>wrote:
>
>> Hello,
>>
>> I am trying to build a Kamailio Raspberry Pi for my presentation at
>> AstriCon but the build fails on the very first file (action.c). This was
>> working before (although I was using Fedora on the Pi last time).
>>
>> Has anyone changed anything recently or have any ideas about this?
>>
>> It may be as simple as tweaking the build arguments, but as this worked
>> for me before I thought I'd ask first...
>>
>> Here is the build output:
>> CC (gcc) [kamailio] action.o
>> In file included from parser/../mem/../atomic/atomic_native.h:74:0,
>> from parser/../mem/../futexlock.h:44,
>> from parser/../mem/../lock_ops.h:85,
>> from parser/../mem/shm_mem.h:75,
>> from parser/../ut.h:64,
>> from parser/../ip_addr.h:50,
>> from parser/msg_parser.h:61,
>> from select.h:38,
>> from route_struct.h:47,
>> from action.h:42,
>> from action.c:69:
>> parser/../mem/../atomic/atomic_arm.h:69:2: warning: #warning SMP not
>> supported for arm atomic ops, try compiling with -DNOSMP [-Wcpp]
>> In file included from parser/../mem/../atomic/atomic_arm.h:81:0,
>> from parser/../mem/../atomic/atomic_native.h:74,
>> from parser/../mem/../futexlock.h:44,
>> from parser/../mem/../lock_ops.h:85,
>> from parser/../mem/shm_mem.h:75,
>> from parser/../ut.h:64,
>> from parser/../ip_addr.h:50,
>> from parser/msg_parser.h:61,
>> from select.h:38,
>> from route_struct.h:47,
>> from action.h:42,
>> from action.c:69:
>> parser/../mem/../atomic/atomic_unknown.h:59:2: warning: #warning no
>> native memory barrier implementations, falling back to slow lock based
>> workarround [-Wcpp]
>> parser/../mem/../atomic/atomic_unknown.h:64:1: error: unknown type name
>> ‘gen_lock_t’
>> In file included from parser/../mem/../atomic/atomic_native.h:74:0,
>> from parser/../mem/../futexlock.h:44,
>> from parser/../mem/../lock_ops.h:85,
>> from parser/../mem/shm_mem.h:75,
>> from parser/../ut.h:64,
>> from parser/../ip_addr.h:50,
>> from parser/msg_parser.h:61,
>> from select.h:38,
>> from route_struct.h:47,
>> from action.h:42,
>> from action.c:69:
>> parser/../mem/../atomic/atomic_arm.h: In function ‘mb_atomic_get_int’:
>> parser/../mem/../atomic/atomic_arm.h:229:2: warning: implicit declaration
>> of function ‘lock_release’ [-Wimplicit-function-declaration]
>> parser/../mem/../atomic/atomic_arm.h:229:2: warning: implicit declaration
>> of function ‘lock_get’ [-Wimplicit-function-declaration]
>> make: *** [action.o] Error 1
>>
>> Regards,
>>
>> Peter
>>
>> --
>> Peter Dunkley
>> Technical Director
>> Crocodile RCS Ltd
>>
>
>
>
> --
> Peter Dunkley
> Technical Director
> Crocodile RCS Ltd
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>
>
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Oct 21-24; Miami, Nov 11-13, 2013
- more details about Kamailio trainings at http://www.asipto.com -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20130910/c6b40255/attachment.html>
More information about the sr-dev
mailing list