Issue->Dpdk for arm cortex-a15 compilation

Issue->Dpdk for arm cortex-a15 compilation

[Jimmy Carter]

[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]

Hi All

I am using dpdk16.11.1 and want to use openwrt external toolchain so that I
can cross compile for arm cortex 15
neon.(arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi)
My target board is Tp link archer C2600.
I am have assigned these env variables but still getting compilation error

export
STAGING_DIR=/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
export
PATH=$PATH:/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/bin


export CROSS=arm-openwrt-linux-
export DPDK_TARGET=arm-armv7a-linuxapp-gcc
export DPDK_DIR=$PWD
export DPDK_BUILD=$DPDK_DIR/$DPDK_TARGET
export
CFLAGS+=-I/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
export RTE_SDK=$PWD
export RTE_TARGET=arm-armv7a-linuxapp-gcc
export DPDK_BUILD_DIR=arm-armv7a-linuxapp-gcc


Error:Attached file

Please advise
Does dpdk have support for openwrt (arm cortex a15)

Thanks
Akshay

[-- Attachment #2: dpdk-error.txt --]
[-- Type: text/plain, Size: 2748 bytes --]

make -f /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/mk/rte.sdkconfig.mk checkconfig
make -f /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/mk/rte.sdkconfig.mk \
		headerconfig NODOTCONF=1
make -s depdirs
make -f /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/mk/rte.sdkbuild.mk all
== Build lib
make S=lib -f /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/lib/Makefile -C /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/build/build/lib all
== Build lib/librte_compat
== Build lib/librte_eal
== Build lib/librte_eal/common
== Build lib/librte_eal/linuxapp
== Build lib/librte_eal/linuxapp/eal
arm-openwrt-linux-gcc -Wp,-MD,./.eal_memory.o.d.tmp  -marm -munaligned-access -pthread -fPIC  -march=armv7-a -mtune=cortex-a9 -mfpu=neon -DRTE_MACHINE_CPUFLAG_NEON  -I/home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/build/include -include /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/build/include/rte_config.h -I/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/include -I/home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/lib/librte_eal/linuxapp/eal/include -I/home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/lib/librte_eal/common -I/home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/lib/librte_eal/common/include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wold-style-definition -Wpointer-arith -Wcast-align -Wnested-externs -Wcast-qual -Wformat-nonliteral -Wformat-security -Wundef -Wwrite-strings -Wno-error=cast-align -O3    --sysroot=/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/include -o eal_memory.o -c /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/lib/librte_eal/linuxapp/eal/eal_memory.c 
In file included from /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/build/include/generic/rte_spinlock.h:50:0,
                 from /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/build/include/rte_spinlock.h:45,
                 from /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/build/include/rte_malloc_heap.h:39,
                 from /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/build/include/rte_eal_memconfig.h:40,
                 from /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/lib/librte_eal/linuxapp/eal/eal_memory.c:92:
/home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/build/include/rte_lcore.h:56:10: error: unknown type name 'cpu_set_t'
  typedef cpu_set_t rte_cpuset_t;
          ^
make[5]: *** [eal_memory.o] Error 1
make[4]: *** [eal] Error 2
make[3]: *** [linuxapp] Error 2
make[2]: *** [librte_eal] Error 2
make[1]: *** [lib] Error 2
make: *** [all] Error 2

Re: Issue->Dpdk for arm cortex-a15 compilation

[Jan Viktorin]

Hello Jimmy,

On Tue, 16 May 2017 15:38:22 +0530
Jimmy Carter <jimmycarter256@gmail.com> wrote:

> Hi All
> 
> I am using dpdk16.11.1 and want to use openwrt external toolchain so that I
> can cross compile for arm cortex 15
> neon.(arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi)

I've never built DPDK with musl-eabi. I don't think that your issue is
related but just note that my builds have always been done with gnueabi.

> My target board is Tp link archer C2600.
> I am have assigned these env variables but still getting compilation error
> 
> export
> STAGING_DIR=/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
> export
> PATH=$PATH:/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/bin
> 
> 
> export CROSS=arm-openwrt-linux-
> export DPDK_TARGET=arm-armv7a-linuxapp-gcc
> export DPDK_DIR=$PWD
> export DPDK_BUILD=$DPDK_DIR/$DPDK_TARGET
> export
> CFLAGS+=-I/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
> export RTE_SDK=$PWD
> export RTE_TARGET=arm-armv7a-linuxapp-gcc
> export DPDK_BUILD_DIR=arm-armv7a-linuxapp-gcc
> 

There is a patch to Buildroot that can help you with the setup. See:

 https://patchwork.ozlabs.org/patch/611383/

> 
> Error:Attached file

Your build fails on

eal_memory.c:92:
/home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/build/include/rte_lcore.h:56:10: error: unknown type name 'cpu_set_t'
  typedef cpu_set_t rte_cpuset_t;

This looks like there is some issue with Linux Kernel headers.

lib/librte_eal/common/include/rte_lcore.h:

 53 #if defined(__linux__)
 54         typedef cpu_set_t rte_cpuset_t;
 55 #elif defined(__FreeBSD__)
 56 #include <pthread_np.h>
 57         typedef cpuset_t rte_cpuset_t;
 58 #endif

Probably, you should set the RTE_KERNELDIR properly.

> 
> Please advise
> Does dpdk have support for openwrt (arm cortex a15)

DPDK does not support OpenWRT because (as far as I know) nobody from
the DPDK community is using it in this way. I build DPDK via Buildroot
but this is unsupported by the DPDK upstream.

I could build DPDK for Cortex-A7, Cortex-A9 and Cortex-A15 in the past.

I run regular builds of the master branch and I can see no breakage
for the arm-armv7a-linuxapp-gcc configuration.

Regards
Jan

> 
> Thanks
> Akshay

Re: [dpdk-maintainers] Issue->Dpdk for arm cortex-a15 compilation

[Thomas Monjalon]

16/05/2017 12:51, Jan Viktorin:
> DPDK does not support OpenWRT because (as far as I know) nobody from
> the DPDK community is using it in this way. I build DPDK via Buildroot
> but this is unsupported by the DPDK upstream.

Why means "unsupported upstream"? Are we missing some patches?
Should we integrate Buildroot compilation in our CI?

Re: [dpdk-maintainers] Issue->Dpdk for arm cortex-a15 compilation

[Jan Viktorin]

On Tue, 16 May 2017 13:22:19 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:

> 16/05/2017 12:51, Jan Viktorin:
> > DPDK does not support OpenWRT because (as far as I know) nobody from
> > the DPDK community is using it in this way. I build DPDK via Buildroot
> > but this is unsupported by the DPDK upstream.  
> 
> Why means "unsupported upstream"? Are we missing some patches?

I mean that DPDK does not contain anything related to Buildroot in its
repositories and it is not related to it in any way... It does not mean
whether it does or does not work.

And also, I've never finished my Builroot integration into the Buildroot
upstream.

> Should we integrate Buildroot compilation in our CI?

Well, I do it. If the support is upstreamed into the Buildroot master,
I'd say yes, It would be a good idea to include it in the DPDK CI. This
is about having somebody to do it...

Regards
Jan

-- 
   Jan Viktorin                  E-mail: Viktorin@RehiveTech.com
   System Architect              Web:    www.RehiveTech.com
   RehiveTech
   Brno, Czech Republic

Re: Issue->Dpdk for arm cortex-a15 compilation

[Neil Horman]

On Tue, May 16, 2017 at 12:51:40PM +0200, Jan Viktorin wrote:
> Hello Jimmy,
> 
> On Tue, 16 May 2017 15:38:22 +0530
> Jimmy Carter <jimmycarter256@gmail.com> wrote:
> 
> > Hi All
> > 
> > I am using dpdk16.11.1 and want to use openwrt external toolchain so that I
> > can cross compile for arm cortex 15
> > neon.(arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi)
> 
> I've never built DPDK with musl-eabi. I don't think that your issue is
> related but just note that my builds have always been done with gnueabi.
> 
> > My target board is Tp link archer C2600.
> > I am have assigned these env variables but still getting compilation error
> > 
> > export
> > STAGING_DIR=/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
> > export
> > PATH=$PATH:/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/bin
> > 
> > 
> > export CROSS=arm-openwrt-linux-
> > export DPDK_TARGET=arm-armv7a-linuxapp-gcc
> > export DPDK_DIR=$PWD
> > export DPDK_BUILD=$DPDK_DIR/$DPDK_TARGET
> > export
> > CFLAGS+=-I/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
> > export RTE_SDK=$PWD
> > export RTE_TARGET=arm-armv7a-linuxapp-gcc
> > export DPDK_BUILD_DIR=arm-armv7a-linuxapp-gcc
> > 
> 
> There is a patch to Buildroot that can help you with the setup. See:
> 
>  https://patchwork.ozlabs.org/patch/611383/
> 
> > 
> > Error:Attached file
> 
> Your build fails on
> 
> eal_memory.c:92:
> /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/build/include/rte_lcore.h:56:10: error: unknown type name 'cpu_set_t'
>   typedef cpu_set_t rte_cpuset_t;
> 
> This looks like there is some issue with Linux Kernel headers.
> 
> lib/librte_eal/common/include/rte_lcore.h:
> 
>  53 #if defined(__linux__)
>  54         typedef cpu_set_t rte_cpuset_t;
>  55 #elif defined(__FreeBSD__)
>  56 #include <pthread_np.h>
>  57         typedef cpuset_t rte_cpuset_t;
>  58 #endif
> 
> Probably, you should set the RTE_KERNELDIR properly.
> 
I don't think so.  cpu_set_t is most recently defined in
/usr/include/bits/shced.h, which is a glibc header.  What version of glibc are
you building with?

Neil

> > 
> > Please advise
> > Does dpdk have support for openwrt (arm cortex a15)
> 
> DPDK does not support OpenWRT because (as far as I know) nobody from
> the DPDK community is using it in this way. I build DPDK via Buildroot
> but this is unsupported by the DPDK upstream.
> 
> I could build DPDK for Cortex-A7, Cortex-A9 and Cortex-A15 in the past.
> 
> I run regular builds of the master branch and I can see no breakage
> for the arm-armv7a-linuxapp-gcc configuration.
> 
> Regards
> Jan
> 
> > 
> > Thanks
> > Akshay
> 

Re: Issue->Dpdk for arm cortex-a15 compilation

[Jan Viktorin]

On Tue, 16 May 2017 07:44:59 -0400
Neil Horman <nhorman@tuxdriver.com> wrote:

> On Tue, May 16, 2017 at 12:51:40PM +0200, Jan Viktorin wrote:
> > Hello Jimmy,
> > 
> > On Tue, 16 May 2017 15:38:22 +0530
> > Jimmy Carter <jimmycarter256@gmail.com> wrote:
> >   
> > > Hi All
> > > 
> > > I am using dpdk16.11.1 and want to use openwrt external toolchain so that I
> > > can cross compile for arm cortex 15
> > > neon.(arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi)  
> > 
> > I've never built DPDK with musl-eabi. I don't think that your issue is
> > related but just note that my builds have always been done with gnueabi.
> >   
> > > My target board is Tp link archer C2600.
> > > I am have assigned these env variables but still getting compilation error
> > > 
> > > export
> > > STAGING_DIR=/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
> > > export
> > > PATH=$PATH:/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/bin
> > > 
> > > 
> > > export CROSS=arm-openwrt-linux-
> > > export DPDK_TARGET=arm-armv7a-linuxapp-gcc
> > > export DPDK_DIR=$PWD
> > > export DPDK_BUILD=$DPDK_DIR/$DPDK_TARGET
> > > export
> > > CFLAGS+=-I/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
> > > export RTE_SDK=$PWD
> > > export RTE_TARGET=arm-armv7a-linuxapp-gcc
> > > export DPDK_BUILD_DIR=arm-armv7a-linuxapp-gcc
> > >   
> > 
> > There is a patch to Buildroot that can help you with the setup. See:
> > 
> >  https://patchwork.ozlabs.org/patch/611383/
> >   
> > > 
> > > Error:Attached file  
> > 
> > Your build fails on
> > 
> > eal_memory.c:92:
> > /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/build/include/rte_lcore.h:56:10: error: unknown type name 'cpu_set_t'
> >   typedef cpu_set_t rte_cpuset_t;
> > 
> > This looks like there is some issue with Linux Kernel headers.
> > 
> > lib/librte_eal/common/include/rte_lcore.h:
> > 
> >  53 #if defined(__linux__)
> >  54         typedef cpu_set_t rte_cpuset_t;
> >  55 #elif defined(__FreeBSD__)
> >  56 #include <pthread_np.h>
> >  57         typedef cpuset_t rte_cpuset_t;
> >  58 #endif
> > 
> > Probably, you should set the RTE_KERNELDIR properly.
> >   
> I don't think so.  cpu_set_t is most recently defined in
> /usr/include/bits/shced.h, which is a glibc header.  What version of glibc are
> you building with?

So, in that case, it can be related to the musl libc (no glibc at all)
as I pointed above...

Jan

> 
> Neil
> 
> > > 
> > > Please advise
> > > Does dpdk have support for openwrt (arm cortex a15)  
> > 
> > DPDK does not support OpenWRT because (as far as I know) nobody from
> > the DPDK community is using it in this way. I build DPDK via Buildroot
> > but this is unsupported by the DPDK upstream.
> > 
> > I could build DPDK for Cortex-A7, Cortex-A9 and Cortex-A15 in the past.
> > 
> > I run regular builds of the master branch and I can see no breakage
> > for the arm-armv7a-linuxapp-gcc configuration.
> > 
> > Regards
> > Jan
> >   
> > > 
> > > Thanks
> > > Akshay  
> >   



-- 
   Jan Viktorin                  E-mail: Viktorin@RehiveTech.com
   System Architect              Web:    www.RehiveTech.com
   RehiveTech
   Brno, Czech Republic

Re: Issue->Dpdk for arm cortex-a15 compilation

[Jimmy Carter]

[-- Attachment #1: Type: text/plain, Size: 3509 bytes --]

Hi All

Attached is the complete env variables file
I have added RTE_KERNELDIR too
Also I am  now using gnu-eabi version 5.4.0
[arm-openwrt-linux-muslgnueabi-gcc (LEDE GCC 5.4.0 r3909-6411a12) 5.4.0]
But I am still getting the same error

Currently I am not using buildroot
Is there any step by step available guide for cross compiling dpdk using
buildroot for target arm cortex-a15 using some external toolchain.
I found this http://dpdk.org/ml/archives/announce/2015-October/000066.html


Please advise



Thanks

On Tue, May 16, 2017 at 5:14 PM, Neil Horman <nhorman@tuxdriver.com> wrote:

> On Tue, May 16, 2017 at 12:51:40PM +0200, Jan Viktorin wrote:
> > Hello Jimmy,
> >
> > On Tue, 16 May 2017 15:38:22 +0530
> > Jimmy Carter <jimmycarter256@gmail.com> wrote:
> >
> > > Hi All
> > >
> > > I am using dpdk16.11.1 and want to use openwrt external toolchain so
> that I
> > > can cross compile for arm cortex 15
> > > neon.(arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi)
> >
> > I've never built DPDK with musl-eabi. I don't think that your issue is
> > related but just note that my builds have always been done with gnueabi.
> >
> > > My target board is Tp link archer C2600.
> > > I am have assigned these env variables but still getting compilation
> error
> > >
> > > export
> > > STAGING_DIR=/home/xav-101000739/ovslede/source/
> staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
> > > export
> > > PATH=$PATH:/home/xav-101000739/ovslede/source/
> staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/bin
> > >
> > >
> > > export CROSS=arm-openwrt-linux-
> > > export DPDK_TARGET=arm-armv7a-linuxapp-gcc
> > > export DPDK_DIR=$PWD
> > > export DPDK_BUILD=$DPDK_DIR/$DPDK_TARGET
> > > export
> > > CFLAGS+=-I/home/xav-101000739/ovslede/source/staging_dir/
> toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
> > > export RTE_SDK=$PWD
> > > export RTE_TARGET=arm-armv7a-linuxapp-gcc
> > > export DPDK_BUILD_DIR=arm-armv7a-linuxapp-gcc
> > >
> >
> > There is a patch to Buildroot that can help you with the setup. See:
> >
> >  https://patchwork.ozlabs.org/patch/611383/
> >
> > >
> > > Error:Attached file
> >
> > Your build fails on
> >
> > eal_memory.c:92:
> > /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/
> build/include/rte_lcore.h:56:10: error: unknown type name 'cpu_set_t'
> >   typedef cpu_set_t rte_cpuset_t;
> >
> > This looks like there is some issue with Linux Kernel headers.
> >
> > lib/librte_eal/common/include/rte_lcore.h:
> >
> >  53 #if defined(__linux__)
> >  54         typedef cpu_set_t rte_cpuset_t;
> >  55 #elif defined(__FreeBSD__)
> >  56 #include <pthread_np.h>
> >  57         typedef cpuset_t rte_cpuset_t;
> >  58 #endif
> >
> > Probably, you should set the RTE_KERNELDIR properly.
> >
> I don't think so.  cpu_set_t is most recently defined in
> /usr/include/bits/shced.h, which is a glibc header.  What version of glibc
> are
> you building with?
>
> Neil
>
> > >
> > > Please advise
> > > Does dpdk have support for openwrt (arm cortex a15)
> >
> > DPDK does not support OpenWRT because (as far as I know) nobody from
> > the DPDK community is using it in this way. I build DPDK via Buildroot
> > but this is unsupported by the DPDK upstream.
> >
> > I could build DPDK for Cortex-A7, Cortex-A9 and Cortex-A15 in the past.
> >
> > I run regular builds of the master branch and I can see no breakage
> > for the arm-armv7a-linuxapp-gcc configuration.
> >
> > Regards
> > Jan
> >
> > >
> > > Thanks
> > > Akshay
> >
>

[-- Attachment #2: env-dpdk.txt --]
[-- Type: text/plain, Size: 3008 bytes --]

DPDK_BUILD_DIR=arm-armv7a-linuxapp-gcc
COMP_WORDBREAKS= 	
"'><;|&(:
SHELL=/bin/bash
TERM=xterm
EXTRA_LDLIBS=-L/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/lib
OLDPWD=/usr/src/dpdk-16.11/examples
USER=root
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:
SUDO_USER=xav-101000739
SUDO_UID=1000
DPDK_BUILD=/usr/src/dpdk-16.11/arm-armv7a-linuxapp-gcc
USERNAME=root
DPDK_TARGET=arm-armv7a-linuxapp-gcc
DPDK_DIR=/usr/src/dpdk-16.11
MAIL=/var/mail/root
PATH=/home/xav-101000739/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/bin
RTE_SDK=/usr/src/dpdk-16.11
RTE_TARGET=arm-armv7a-linuxapp-gcc
PWD=/usr/src/dpdk-16.11
LANG=en_IN
SHLVL=1
SUDO_COMMAND=/bin/bash
HOME=/home/xav-101000739
RTE_KERNELDIR=/home/xav-101000739/ovslede/source/build_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/linux-4.9.20
LANGUAGE=en_IN:en
CFLAGS=-I/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
STAGING_DIR=/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
LOGNAME=root
WIRESHARK=/usr/include/wireshark
LESSOPEN=| /usr/bin/lesspipe %s
ARCH=arm
CROSS=arm-openwrt-linux-muslgnueabi-
EXTRA_CFLAGS=-I/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/include
SUDO_GID=1000
DISPLAY=:0
LESSCLOSE=/usr/bin/lesspipe %s %s
EXTRA_LDFLAGS=-L/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/lib
COLORTERM=gnome-terminal
XAUTHORITY=/home/xav-101000739/.Xauthority
_=/usr/bin/env

Re: Issue->Dpdk for arm cortex-a15 compilation

[Jan Viktorin]

On Tue, 16 May 2017 17:25:20 +0530
Jimmy Carter <jimmycarter256@gmail.com> wrote:

> Hi All
> 
> Attached is the complete env variables file
> I have added RTE_KERNELDIR too
> Also I am  now using gnu-eabi version 5.4.0
> [arm-openwrt-linux-muslgnueabi-gcc (LEDE GCC 5.4.0 r3909-6411a12) 5.4.0]
> But I am still getting the same error
> 
> Currently I am not using buildroot
> Is there any step by step available guide for cross compiling dpdk using
> buildroot for target arm cortex-a15 using some external toolchain.
> I found this http://dpdk.org/ml/archives/announce/2015-October/000066.html

This short tutorial points to some older version of the Buildroot
support. That was before the ARM support has been merged into DPDK.

I've just pushed the branch dpdk-support-v5 (d25ddaadf2) into
the RehiveTech repository. It contains the latest patch sent to the
Buildroot mailing list [1] and some more. By the way, it cleanly
applies to the latest Buildroot master as well.

This branch assumes DPDK 16.04 which is quite old but if you drop the
0001-mk-do-not-enforce-any-specific-ARM-ABI.patch, it might work for newer
DPDK as well.

Steps:

$ git clone https://github.com/RehiveTech/buildroot
$ cd buildroot
$ make qemu_arm_vexpress_defconfig
$ make menuconfig

 * set libc library to glibc
 * enable DPDK in Target packages/Libraries/Networking/DPDK

$ make linux-menuconfig

 * enable UIO, PCI and MSI-X (if applicable)

$ make

I didn't test it myself recently but I belive that it should work well.
Instead of qemu_arm_vexpress_defconfig, you should select your target
board, if applicable.

I hope, it would help you.

Regards
Jan

[1] https://patchwork.ozlabs.org/patch/611383/

> 
> 
> Please advise
> 
> 
> 
> Thanks
> 
> On Tue, May 16, 2017 at 5:14 PM, Neil Horman <nhorman@tuxdriver.com> wrote:
> 
> > On Tue, May 16, 2017 at 12:51:40PM +0200, Jan Viktorin wrote:  
> > > Hello Jimmy,
> > >
> > > On Tue, 16 May 2017 15:38:22 +0530
> > > Jimmy Carter <jimmycarter256@gmail.com> wrote:
> > >  
> > > > Hi All
> > > >
> > > > I am using dpdk16.11.1 and want to use openwrt external toolchain so  
> > that I  
> > > > can cross compile for arm cortex 15
> > > > neon.(arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi)  
> > >
> > > I've never built DPDK with musl-eabi. I don't think that your issue is
> > > related but just note that my builds have always been done with gnueabi.
> > >  
> > > > My target board is Tp link archer C2600.
> > > > I am have assigned these env variables but still getting compilation  
> > error  
> > > >
> > > > export
> > > > STAGING_DIR=/home/xav-101000739/ovslede/source/  
> > staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi  
> > > > export
> > > > PATH=$PATH:/home/xav-101000739/ovslede/source/  
> > staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/bin  
> > > >
> > > >
> > > > export CROSS=arm-openwrt-linux-
> > > > export DPDK_TARGET=arm-armv7a-linuxapp-gcc
> > > > export DPDK_DIR=$PWD
> > > > export DPDK_BUILD=$DPDK_DIR/$DPDK_TARGET
> > > > export
> > > > CFLAGS+=-I/home/xav-101000739/ovslede/source/staging_dir/  
> > toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi  
> > > > export RTE_SDK=$PWD
> > > > export RTE_TARGET=arm-armv7a-linuxapp-gcc
> > > > export DPDK_BUILD_DIR=arm-armv7a-linuxapp-gcc
> > > >  
> > >
> > > There is a patch to Buildroot that can help you with the setup. See:
> > >
> > >  https://patchwork.ozlabs.org/patch/611383/
> > >  
> > > >
> > > > Error:Attached file  
> > >
> > > Your build fails on
> > >
> > > eal_memory.c:92:
> > > /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/  
> > build/include/rte_lcore.h:56:10: error: unknown type name 'cpu_set_t'  
> > >   typedef cpu_set_t rte_cpuset_t;
> > >
> > > This looks like there is some issue with Linux Kernel headers.
> > >
> > > lib/librte_eal/common/include/rte_lcore.h:
> > >
> > >  53 #if defined(__linux__)
> > >  54         typedef cpu_set_t rte_cpuset_t;
> > >  55 #elif defined(__FreeBSD__)
> > >  56 #include <pthread_np.h>
> > >  57         typedef cpuset_t rte_cpuset_t;
> > >  58 #endif
> > >
> > > Probably, you should set the RTE_KERNELDIR properly.
> > >  
> > I don't think so.  cpu_set_t is most recently defined in
> > /usr/include/bits/shced.h, which is a glibc header.  What version of glibc
> > are
> > you building with?
> >
> > Neil
> >  
> > > >
> > > > Please advise
> > > > Does dpdk have support for openwrt (arm cortex a15)  
> > >
> > > DPDK does not support OpenWRT because (as far as I know) nobody from
> > > the DPDK community is using it in this way. I build DPDK via Buildroot
> > > but this is unsupported by the DPDK upstream.
> > >
> > > I could build DPDK for Cortex-A7, Cortex-A9 and Cortex-A15 in the past.
> > >
> > > I run regular builds of the master branch and I can see no breakage
> > > for the arm-armv7a-linuxapp-gcc configuration.
> > >
> > > Regards
> > > Jan
> > >  
> > > >
> > > > Thanks
> > > > Akshay  
> > >  
> >  



-- 
   Jan Viktorin                  E-mail: Viktorin@RehiveTech.com
   System Architect              Web:    www.RehiveTech.com
   RehiveTech
   Brno, Czech Republic

Re: Issue->Dpdk for arm cortex-a15 compilation

[Jimmy Carter]

I assume after git clone https://github.com/RehiveTech/buildroot
 I need to git checkout dpdk-support-v5
I get legacy error on running make
root@xav101000739:~/Downloads/dpdk/newbuildroot/buildroot# *make *
*Makefile.legacy:12: *** "You have legacy configuration in your .config!
Please check your configuration.".  Stop.*


Thanks

On Tue, May 16, 2017 at 5:58 PM, Jan Viktorin <viktorin@rehivetech.com>
wrote:

> On Tue, 16 May 2017 17:25:20 +0530
> Jimmy Carter <jimmycarter256@gmail.com> wrote:
>
> > Hi All
> >
> > Attached is the complete env variables file
> > I have added RTE_KERNELDIR too
> > Also I am  now using gnu-eabi version 5.4.0
> > [arm-openwrt-linux-muslgnueabi-gcc (LEDE GCC 5.4.0 r3909-6411a12) 5.4.0]
> > But I am still getting the same error
> >
> > Currently I am not using buildroot
> > Is there any step by step available guide for cross compiling dpdk using
> > buildroot for target arm cortex-a15 using some external toolchain.
> > I found this http://dpdk.org/ml/archives/announce/2015-October/000066.
> html
>
> This short tutorial points to some older version of the Buildroot
> support. That was before the ARM support has been merged into DPDK.
>
> I've just pushed the branch dpdk-support-v5 (d25ddaadf2) into
> the RehiveTech repository. It contains the latest patch sent to the
> Buildroot mailing list [1] and some more. By the way, it cleanly
> applies to the latest Buildroot master as well.
>
> This branch assumes DPDK 16.04 which is quite old but if you drop the
> 0001-mk-do-not-enforce-any-specific-ARM-ABI.patch, it might work for newer
> DPDK as well.
>
> Steps:
>
> $ git clone https://github.com/RehiveTech/buildroot
> $ cd buildroot
> $ make qemu_arm_vexpress_defconfig
> $ make menuconfig
>
>  * set libc library to glibc
>  * enable DPDK in Target packages/Libraries/Networking/DPDK
>
> $ make linux-menuconfig
>
>  * enable UIO, PCI and MSI-X (if applicable)
>
> $ make
>
> I didn't test it myself recently but I belive that it should work well.
> Instead of qemu_arm_vexpress_defconfig, you should select your target
> board, if applicable.
>
> I hope, it would help you.
>
> Regards
> Jan
>
> [1] https://patchwork.ozlabs.org/patch/611383/
>
> >
> >
> > Please advise
> >
> >
> >
> > Thanks
> >
> > On Tue, May 16, 2017 at 5:14 PM, Neil Horman <nhorman@tuxdriver.com>
> wrote:
> >
> > > On Tue, May 16, 2017 at 12:51:40PM +0200, Jan Viktorin wrote:
> > > > Hello Jimmy,
> > > >
> > > > On Tue, 16 May 2017 15:38:22 +0530
> > > > Jimmy Carter <jimmycarter256@gmail.com> wrote:
> > > >
> > > > > Hi All
> > > > >
> > > > > I am using dpdk16.11.1 and want to use openwrt external toolchain
> so
> > > that I
> > > > > can cross compile for arm cortex 15
> > > > > neon.(arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi)
> > > >
> > > > I've never built DPDK with musl-eabi. I don't think that your issue
> is
> > > > related but just note that my builds have always been done with
> gnueabi.
> > > >
> > > > > My target board is Tp link archer C2600.
> > > > > I am have assigned these env variables but still getting
> compilation
> > > error
> > > > >
> > > > > export
> > > > > STAGING_DIR=/home/xav-101000739/ovslede/source/
> > > staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
> > > > > export
> > > > > PATH=$PATH:/home/xav-101000739/ovslede/source/
> > > staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.
> 0_musl_eabi/bin
> > > > >
> > > > >
> > > > > export CROSS=arm-openwrt-linux-
> > > > > export DPDK_TARGET=arm-armv7a-linuxapp-gcc
> > > > > export DPDK_DIR=$PWD
> > > > > export DPDK_BUILD=$DPDK_DIR/$DPDK_TARGET
> > > > > export
> > > > > CFLAGS+=-I/home/xav-101000739/ovslede/source/staging_dir/
> > > toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
> > > > > export RTE_SDK=$PWD
> > > > > export RTE_TARGET=arm-armv7a-linuxapp-gcc
> > > > > export DPDK_BUILD_DIR=arm-armv7a-linuxapp-gcc
> > > > >
> > > >
> > > > There is a patch to Buildroot that can help you with the setup. See:
> > > >
> > > >  https://patchwork.ozlabs.org/patch/611383/
> > > >
> > > > >
> > > > > Error:Attached file
> > > >
> > > > Your build fails on
> > > >
> > > > eal_memory.c:92:
> > > > /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/
> > > build/include/rte_lcore.h:56:10: error: unknown type name 'cpu_set_t'
> > > >   typedef cpu_set_t rte_cpuset_t;
> > > >
> > > > This looks like there is some issue with Linux Kernel headers.
> > > >
> > > > lib/librte_eal/common/include/rte_lcore.h:
> > > >
> > > >  53 #if defined(__linux__)
> > > >  54         typedef cpu_set_t rte_cpuset_t;
> > > >  55 #elif defined(__FreeBSD__)
> > > >  56 #include <pthread_np.h>
> > > >  57         typedef cpuset_t rte_cpuset_t;
> > > >  58 #endif
> > > >
> > > > Probably, you should set the RTE_KERNELDIR properly.
> > > >
> > > I don't think so.  cpu_set_t is most recently defined in
> > > /usr/include/bits/shced.h, which is a glibc header.  What version of
> glibc
> > > are
> > > you building with?
> > >
> > > Neil
> > >
> > > > >
> > > > > Please advise
> > > > > Does dpdk have support for openwrt (arm cortex a15)
> > > >
> > > > DPDK does not support OpenWRT because (as far as I know) nobody from
> > > > the DPDK community is using it in this way. I build DPDK via
> Buildroot
> > > > but this is unsupported by the DPDK upstream.
> > > >
> > > > I could build DPDK for Cortex-A7, Cortex-A9 and Cortex-A15 in the
> past.
> > > >
> > > > I run regular builds of the master branch and I can see no breakage
> > > > for the arm-armv7a-linuxapp-gcc configuration.
> > > >
> > > > Regards
> > > > Jan
> > > >
> > > > >
> > > > > Thanks
> > > > > Akshay
> > > >
> > >
>
>
>
> --
>    Jan Viktorin                  E-mail: Viktorin@RehiveTech.com
>    System Architect              Web:    www.RehiveTech.com
>    RehiveTech
>    Brno, Czech Republic
>

Re: Issue->Dpdk for arm cortex-a15 compilation

[Jan Viktorin]

On Tue, 16 May 2017 18:57:41 +0530
Jimmy Carter <jimmycarter256@gmail.com> wrote:

> I assume after git clone https://github.com/RehiveTech/buildroot
>  I need to git checkout dpdk-support-v5

Yes, I forgot to mention...

> I get legacy error on running make
> root@xav101000739:~/Downloads/dpdk/newbuildroot/buildroot# *make *
> *Makefile.legacy:12: *** "You have legacy configuration in your .config!
> Please check your configuration.".  Stop.*

This is very strange. Did you use qemu_arm_vexpress_defconfig or some
other?

I didn't have any issue during the build except of a mismatch in the
SHA256 checksum of the dpdk-16.04.tar.gz which is strange. After
fixing:

diff --git a/package/dpdk/dpdk.hash b/package/dpdk/dpdk.hash
index 3780c665b..c0158e477 100644
--- a/package/dpdk/dpdk.hash
+++ b/package/dpdk/dpdk.hash
@@ -1,2 +1,2 @@
 # Locally calculated
-sha256 d631495bc6e8d4c4aec72999ac03c3ce213bb996cb88f3bf14bb980dad1d3f7b  dpdk-16.04.tar.gz
+sha256 f917875b1432adaaebb2761c154623bb101e0308153aa011f06a69bd1e9e98fb  dpdk-16.04.tar.gz

it works.

$ ls output/images/
rootfs.ext2  vexpress-v2p-ca9.dtb  zImage

Regards
Jan

> 
> 
> Thanks
> 
> On Tue, May 16, 2017 at 5:58 PM, Jan Viktorin <viktorin@rehivetech.com>
> wrote:
> 
> > On Tue, 16 May 2017 17:25:20 +0530
> > Jimmy Carter <jimmycarter256@gmail.com> wrote:
> >  
> > > Hi All
> > >
> > > Attached is the complete env variables file
> > > I have added RTE_KERNELDIR too
> > > Also I am  now using gnu-eabi version 5.4.0
> > > [arm-openwrt-linux-muslgnueabi-gcc (LEDE GCC 5.4.0 r3909-6411a12) 5.4.0]
> > > But I am still getting the same error
> > >
> > > Currently I am not using buildroot
> > > Is there any step by step available guide for cross compiling dpdk using
> > > buildroot for target arm cortex-a15 using some external toolchain.
> > > I found this http://dpdk.org/ml/archives/announce/2015-October/000066.  
> > html
> >
> > This short tutorial points to some older version of the Buildroot
> > support. That was before the ARM support has been merged into DPDK.
> >
> > I've just pushed the branch dpdk-support-v5 (d25ddaadf2) into
> > the RehiveTech repository. It contains the latest patch sent to the
> > Buildroot mailing list [1] and some more. By the way, it cleanly
> > applies to the latest Buildroot master as well.
> >
> > This branch assumes DPDK 16.04 which is quite old but if you drop the
> > 0001-mk-do-not-enforce-any-specific-ARM-ABI.patch, it might work for newer
> > DPDK as well.
> >
> > Steps:
> >
> > $ git clone https://github.com/RehiveTech/buildroot
> > $ cd buildroot
> > $ make qemu_arm_vexpress_defconfig
> > $ make menuconfig
> >
> >  * set libc library to glibc
> >  * enable DPDK in Target packages/Libraries/Networking/DPDK
> >
> > $ make linux-menuconfig
> >
> >  * enable UIO, PCI and MSI-X (if applicable)
> >
> > $ make
> >
> > I didn't test it myself recently but I belive that it should work well.
> > Instead of qemu_arm_vexpress_defconfig, you should select your target
> > board, if applicable.
> >
> > I hope, it would help you.
> >
> > Regards
> > Jan
> >
> > [1] https://patchwork.ozlabs.org/patch/611383/
> >  
> > >
> > >
> > > Please advise
> > >
> > >
> > >
> > > Thanks
> > >
> > > On Tue, May 16, 2017 at 5:14 PM, Neil Horman <nhorman@tuxdriver.com>  
> > wrote:  
> > >  
> > > > On Tue, May 16, 2017 at 12:51:40PM +0200, Jan Viktorin wrote:  
> > > > > Hello Jimmy,
> > > > >
> > > > > On Tue, 16 May 2017 15:38:22 +0530
> > > > > Jimmy Carter <jimmycarter256@gmail.com> wrote:
> > > > >  
> > > > > > Hi All
> > > > > >
> > > > > > I am using dpdk16.11.1 and want to use openwrt external toolchain  
> > so  
> > > > that I  
> > > > > > can cross compile for arm cortex 15
> > > > > > neon.(arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi)  
> > > > >
> > > > > I've never built DPDK with musl-eabi. I don't think that your issue  
> > is  
> > > > > related but just note that my builds have always been done with  
> > gnueabi.  
> > > > >  
> > > > > > My target board is Tp link archer C2600.
> > > > > > I am have assigned these env variables but still getting  
> > compilation  
> > > > error  
> > > > > >
> > > > > > export
> > > > > > STAGING_DIR=/home/xav-101000739/ovslede/source/  
> > > > staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi  
> > > > > > export
> > > > > > PATH=$PATH:/home/xav-101000739/ovslede/source/  
> > > > staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.  
> > 0_musl_eabi/bin  
> > > > > >
> > > > > >
> > > > > > export CROSS=arm-openwrt-linux-
> > > > > > export DPDK_TARGET=arm-armv7a-linuxapp-gcc
> > > > > > export DPDK_DIR=$PWD
> > > > > > export DPDK_BUILD=$DPDK_DIR/$DPDK_TARGET
> > > > > > export
> > > > > > CFLAGS+=-I/home/xav-101000739/ovslede/source/staging_dir/  
> > > > toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi  
> > > > > > export RTE_SDK=$PWD
> > > > > > export RTE_TARGET=arm-armv7a-linuxapp-gcc
> > > > > > export DPDK_BUILD_DIR=arm-armv7a-linuxapp-gcc
> > > > > >  
> > > > >
> > > > > There is a patch to Buildroot that can help you with the setup. See:
> > > > >
> > > > >  https://patchwork.ozlabs.org/patch/611383/
> > > > >  
> > > > > >
> > > > > > Error:Attached file  
> > > > >
> > > > > Your build fails on
> > > > >
> > > > > eal_memory.c:92:
> > > > > /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/  
> > > > build/include/rte_lcore.h:56:10: error: unknown type name 'cpu_set_t'  
> > > > >   typedef cpu_set_t rte_cpuset_t;
> > > > >
> > > > > This looks like there is some issue with Linux Kernel headers.
> > > > >
> > > > > lib/librte_eal/common/include/rte_lcore.h:
> > > > >
> > > > >  53 #if defined(__linux__)
> > > > >  54         typedef cpu_set_t rte_cpuset_t;
> > > > >  55 #elif defined(__FreeBSD__)
> > > > >  56 #include <pthread_np.h>
> > > > >  57         typedef cpuset_t rte_cpuset_t;
> > > > >  58 #endif
> > > > >
> > > > > Probably, you should set the RTE_KERNELDIR properly.
> > > > >  
> > > > I don't think so.  cpu_set_t is most recently defined in
> > > > /usr/include/bits/shced.h, which is a glibc header.  What version of  
> > glibc  
> > > > are
> > > > you building with?
> > > >
> > > > Neil
> > > >  
> > > > > >
> > > > > > Please advise
> > > > > > Does dpdk have support for openwrt (arm cortex a15)  
> > > > >
> > > > > DPDK does not support OpenWRT because (as far as I know) nobody from
> > > > > the DPDK community is using it in this way. I build DPDK via  
> > Buildroot  
> > > > > but this is unsupported by the DPDK upstream.
> > > > >
> > > > > I could build DPDK for Cortex-A7, Cortex-A9 and Cortex-A15 in the  
> > past.  
> > > > >
> > > > > I run regular builds of the master branch and I can see no breakage
> > > > > for the arm-armv7a-linuxapp-gcc configuration.
> > > > >
> > > > > Regards
> > > > > Jan
> > > > >  
> > > > > >
> > > > > > Thanks
> > > > > > Akshay  
> > > > >  
> > > >  
> >
> >
> >
> > --
> >    Jan Viktorin                  E-mail: Viktorin@RehiveTech.com
> >    System Architect              Web:    www.RehiveTech.com
> >    RehiveTech
> >    Brno, Czech Republic
> >  



-- 
   Jan Viktorin                  E-mail: Viktorin@RehiveTech.com
   System Architect              Web:    www.RehiveTech.com
   RehiveTech
   Brno, Czech Republic

Re: Issue->Dpdk for arm cortex-a15 compilation

[Neil Horman]

On Tue, May 16, 2017 at 01:51:52PM +0200, Jan Viktorin wrote:
> On Tue, 16 May 2017 07:44:59 -0400
> Neil Horman <nhorman@tuxdriver.com> wrote:
> 
> > On Tue, May 16, 2017 at 12:51:40PM +0200, Jan Viktorin wrote:
> > > Hello Jimmy,
> > > 
> > > On Tue, 16 May 2017 15:38:22 +0530
> > > Jimmy Carter <jimmycarter256@gmail.com> wrote:
> > >   
> > > > Hi All
> > > > 
> > > > I am using dpdk16.11.1 and want to use openwrt external toolchain so that I
> > > > can cross compile for arm cortex 15
> > > > neon.(arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi)  
> > > 
> > > I've never built DPDK with musl-eabi. I don't think that your issue is
> > > related but just note that my builds have always been done with gnueabi.
> > >   
> > > > My target board is Tp link archer C2600.
> > > > I am have assigned these env variables but still getting compilation error
> > > > 
> > > > export
> > > > STAGING_DIR=/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
> > > > export
> > > > PATH=$PATH:/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi/bin
> > > > 
> > > > 
> > > > export CROSS=arm-openwrt-linux-
> > > > export DPDK_TARGET=arm-armv7a-linuxapp-gcc
> > > > export DPDK_DIR=$PWD
> > > > export DPDK_BUILD=$DPDK_DIR/$DPDK_TARGET
> > > > export
> > > > CFLAGS+=-I/home/xav-101000739/ovslede/source/staging_dir/toolchain-arm_cortex-a15+neon-vfpv4_gcc-5.4.0_musl_eabi
> > > > export RTE_SDK=$PWD
> > > > export RTE_TARGET=arm-armv7a-linuxapp-gcc
> > > > export DPDK_BUILD_DIR=arm-armv7a-linuxapp-gcc
> > > >   
> > > 
> > > There is a patch to Buildroot that can help you with the setup. See:
> > > 
> > >  https://patchwork.ozlabs.org/patch/611383/
> > >   
> > > > 
> > > > Error:Attached file  
> > > 
> > > Your build fails on
> > > 
> > > eal_memory.c:92:
> > > /home/xav-101000739/Downloads/dpdk/dpdk-stable-16.11.1/build/include/rte_lcore.h:56:10: error: unknown type name 'cpu_set_t'
> > >   typedef cpu_set_t rte_cpuset_t;
> > > 
> > > This looks like there is some issue with Linux Kernel headers.
> > > 
> > > lib/librte_eal/common/include/rte_lcore.h:
> > > 
> > >  53 #if defined(__linux__)
> > >  54         typedef cpu_set_t rte_cpuset_t;
> > >  55 #elif defined(__FreeBSD__)
> > >  56 #include <pthread_np.h>
> > >  57         typedef cpuset_t rte_cpuset_t;
> > >  58 #endif
> > > 
> > > Probably, you should set the RTE_KERNELDIR properly.
> > >   
> > I don't think so.  cpu_set_t is most recently defined in
> > /usr/include/bits/shced.h, which is a glibc header.  What version of glibc are
> > you building with?
> 
> So, in that case, it can be related to the musl libc (no glibc at all)
> as I pointed above...
> 
> Jan
> 
I would think so, yes.
Neil

> > 
> > Neil
> > 
> > > > 
> > > > Please advise
> > > > Does dpdk have support for openwrt (arm cortex a15)  
> > > 
> > > DPDK does not support OpenWRT because (as far as I know) nobody from
> > > the DPDK community is using it in this way. I build DPDK via Buildroot
> > > but this is unsupported by the DPDK upstream.
> > > 
> > > I could build DPDK for Cortex-A7, Cortex-A9 and Cortex-A15 in the past.
> > > 
> > > I run regular builds of the master branch and I can see no breakage
> > > for the arm-armv7a-linuxapp-gcc configuration.
> > > 
> > > Regards
> > > Jan
> > >   
> > > > 
> > > > Thanks
> > > > Akshay  
> > >   
> 
> 
> 
> -- 
>    Jan Viktorin                  E-mail: Viktorin@RehiveTech.com
>    System Architect              Web:    www.RehiveTech.com
>    RehiveTech
>    Brno, Czech Republic
>