[OpenSIPS-Users] Cross Compile OpenSIPS ARMv7

Caio caiortp at gmail.com
Tue Oct 20 22:28:17 CEST 2015


Ovidiu Sas,


In the Makefile.defs there a code to get the ARCH

  90 ARCH := $(shell $(GETARCH) |sed -e s/i.86/i386/ -e s/sun4u/sparc64/  \
  91                         -e s/armv4l/arm/ -e "s/Power Macintosh/ppc/" \
  92                         -e s/sun4v/sparc64/ -e "s/cobalt/mips2/" \
  93                         -e s/amd64/x86_64/ )


I tried export ARCH=armv7 but because of the code, the ARCH will be always
x86-64 (host machine) .

I added the CFLAGS to the armv7 arch in the Makefile.defs

 918 ifeq    ($(ARCH), armv7)
 919                 # if gcc
 920 ifeq            ($(CC_NAME), gcc)
 921                                 #common stuff
 922                                  CFLAGS+=-O0 -mfloat-abi=hard
-march=armv7-a -mthumb-interwork -Wcast-align $(PROFILE) \
 923                                 -mfloat-abi=hard -mfpu=neon
-mtune=cortex-a9 -Wall
 924 endif
 925 endif


Which is the best way to pass the arch parameter to the Makefile?

(sorry for the typo in the last email).

Thank you very much.

Best Regards,

Caio Pereira

2015-10-20 17:17 GMT-02:00 Ovidiu Sas <osas at voipembedded.com>:

> The optimizations are done via the compiler flags: CFLAGS.
> You need to replace -09 with -00.
> You need to check if you are using a native compiler or a cross one
> and adjust the proper flags inside Makefile.defs.
>
> Regards,
> Ovidiu Sas
>
> On Tue, Oct 20, 2015 at 1:53 PM, Caio <caiortp at gmail.com> wrote:
> > Hello, Oividiu!
> >
> > Sorry for the delay, I was on vacation.
> >
> > I'm writing a recipe to Yocto.
> > This ARM cpu is new (armv7-a), but I see that is not compatible with
> > opensips's optimization.
> > I'm new with opensips, I have only  tested in my host machine x86-64.
> >
> >
> > Do you know with parameters I need to comment in the Makefile.conf to
> have a
> > basic compilation without any optimization in the opensips?
> >
> >
> > #DEFS+= -DPKG_MALLOC #Uses a faster malloc (exclusive w/ USE_SHM_MEM)
> > #DEFS+= -DSHM_MMAP #Use mmap instead of SYSV shared memory
> > DEFS+= -DUSE_MCAST #Compile in support for IP Multicast
> > DEFS+= -DDISABLE_NAGLE #Disabled the TCP NAgle Algorithm ( lower delay )
> > DEFS+= -DSTATISTICS #Enables the statistics manager
> > DEFS+= -DHAVE_RESOLV_RES #Support for changing some of the resolver
> > parameters
> > #DEFS+= -DHP_MALLOC #High performance allocator with fine-grained locking
> > DEFS+= -DF_MALLOC #An even faster allocator. Not recommended for
> debugging
> > #DEFS+= -DF_MALLOC_OPTIMIZATIONS #Remove all internal checks in F_MALLOC
> > #DEFS+= -DDBG_QM_MALLOC #Allocator used for debugging information
> > #DEFS+= -DUSE_SHM_MEM #All PKG allocations are mapped to SHM ( exclusive
> w/
> > PKG_MALLOC )
> > #DEFS+= -DDBG_F_MALLOC #TODO ?
> > #DEFS+= -DNO_DEBUG #Turns off all debug messages
> > #DEFS+= -DNO_LOG #Completely turns off all the logging
> > #DEFS+= -DVQ_MALLOC #TODO ?
> > #DEFS+= -DFAST_LOCK #Uses fast architecture specific locking
> > #DEFS+= -DUSE_FUTEX #Uses linux futexs with fast architecture specific
> > locking
> > #DEFS+= -DUSE_SYSV_SEM #Uses SYSV sems for locking ( slower & limited
> number
> > of locks
> > #DEFS+= -DUSE_PTHREAD_MUTEX #Uses pthread mutexes
> > #DEFS+= -DBUSY_WAIT #Uses busy waiting on the lock
> > #DEFS+= -DDBG_LOCK #TODO ?
> >
> >
> >
> > Thank you!
> >
> > Best Regards,
> >
> > Caio Pereira
> >
> >
> > 2015-09-23 21:48 GMT-03:00 Ovidiu Sas <osas at voipembedded.com>:
> >>
> >> Hello Caio,
> >>
> >> Have you managed to cross compile opensips?
> >> The optimizations do not work for older type of arm CPUs.
> >> Did you experienced any issues running opensips on arm?
> >>
> >> Regards,
> >> Ovidiu Sas
> >>
> >> On Thu, Sep 17, 2015 at 2:51 PM, Caio <caiortp at gmail.com> wrote:
> >> > Hello,
> >> >
> >> > I would like to cross compile the opensips to ARMv7 architecture
> >> > (Freescale
> >> > IMX6).
> >> > I saw that there's some optimization in assembly to lock functions.
> >> > There's some configuration in the Makeconfig.conf options that I need
> >> > disable or enable to able the opensips run in my target architecutre?
> >> >
> >> > Thank you very much.
> >> >
> >> > Best Regards
> >> >
> >> >
> >> >
> >> > --
> >> > ----------------------------------------------
> >> > Caio Pereira
> >> >
> >> > _______________________________________________
> >> > Users mailing list
> >> > Users at lists.opensips.org
> >> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >> >
> >>
> >>
> >>
> >> --
> >> VoIP Embedded, Inc.
> >> http://www.voipembedded.com
> >>
> >> _______________________________________________
> >> Users mailing list
> >> Users at lists.opensips.org
> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
> >
> >
> > --
> > ----------------------------------------------
> > Caio Pereira
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
>
>
>
> --
> VoIP Embedded, Inc.
> http://www.voipembedded.com
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>



-- 
----------------------------------------------
Caio Pereira
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20151020/b4001991/attachment-0001.htm>


More information about the Users mailing list