Re: [lng-odp] api-next broken?

2017-08-31 Thread Verma, Shally
gt;; Verma, Shally <shally.ve...@cavium.com>; Nilla, Subrahmanyam <subrahmanyam.ni...@cavium.com> Subject: Re: [lng-odp] api-next broken? On 31/08/17 13:25, shally verma wrote: > I was trying api-next from linaro/odp as of today and am seeing this > error. Am I missing anything h

Re: [lng-odp] api-next broken?

2017-08-31 Thread Dmitry Eremin-Solenikov
On 31/08/17 13:25, shally verma wrote: > I was trying api-next from linaro/odp as of today and am seeing this > error. Am I missing anything here? > > I simply use > ./bootstrap > ./configure > ./make > > make[2]: Entering directory >

Re: [lng-odp] api-next broken?

2017-08-31 Thread Maxim Uvarov
-latomic is not installed and ./configure did not detect that. Can you please write compiler version? On 31 August 2017 at 13:25, shally verma wrote: > I was trying api-next from linaro/odp as of today and am seeing this > error. Am I missing anything here? > > I

[lng-odp] api-next broken?

2017-08-31 Thread shally verma
I was trying api-next from linaro/odp as of today and am seeing this error. Am I missing anything here? I simply use ./bootstrap ./configure ./make make[2]: Entering directory `/home/shrutika/zip/zip-linux/83xx/odp/odp/example/ipfragreass' CC odp_ipfragreass-odp_ipfragreass.o CC

Re: [lng-odp] api-next broken?

2015-12-09 Thread Maxim Uvarov
So the problem appears only in libc6-dev 2.21. No problem with libc6-dev 2.19 Diff is: /usr/include/time.h @@ -108,7 +108,7 @@ typedef __timer_t timer_t; #if (!defined __timespec_defined\ && ((defined _TIME_H\ - && (defined

Re: [lng-odp] api-next broken?

2015-12-09 Thread Bill Fischofer
I'm running vanilla Ubuntu 15.04 at current service. gcc shows: bill@Ubuntu15:~/linaro/timefix$ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.9/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu

Re: [lng-odp] api-next broken?

2015-12-09 Thread Maxim Uvarov
yes, I'm installing 15.10 to VM to check that odp works there. Also it looks like in CI we need different containers to check most of common distributive versions. Maxim. On 12/09/2015 15:00, Bill Fischofer wrote: I'm running vanilla Ubuntu 15.04 at current service. gcc shows:

Re: [lng-odp] api-next broken?

2015-12-08 Thread Bill Fischofer
Well, I've verified that if you do similar mods to test/validation/pktio/pktio.c and test/validation/time/time.c then all is good, however what this means is that we've just broken ODP API portability because we now require that ODP applications include this #define when compiling for

Re: [lng-odp] api-next broken?

2015-12-08 Thread Mike Holmes
Patch sent that works for me, it depends on the compiler in use and the c99 vs posix standard I think On 8 December 2015 at 17:14, Bill Fischofer wrote: > git bisect shows: > > 3164ccfe7e6dc548852b8f6f681069cd6d524bfc is the first bad commit > commit

Re: [lng-odp] api-next broken?

2015-12-08 Thread Bill Fischofer
That helps but it looks incomplete. With that patch applied ODP compiles but the CUnit tests fail: Making all in pktio make[3]: Entering directory '/home/bill/linaro/api-next/test/validation/pktio' CC pktio.lo pktio.c: In function 'queue_deq_wait_time': pktio.c:339:13: error: storage

Re: [lng-odp] api-next broken?

2015-12-08 Thread Mike Holmes
Yep, I just compiled what I had, but it is the same root cause, just needs to be told to allow POSIX in that SRC. Maxim do you just want to fix in your morning, I dont have time now tonight so dont wait for me but you could add me as Suggested-by On 8 December 2015 at 18:17, Bill Fischofer

Re: [lng-odp] api-next broken?

2015-12-08 Thread Bill Fischofer
git bisect shows: 3164ccfe7e6dc548852b8f6f681069cd6d524bfc is the first bad commit commit 3164ccfe7e6dc548852b8f6f681069cd6d524bfc Author: Ivan Khoronzhuk Date: Fri Dec 4 19:51:29 2015 +0200 linux-generic: odp_time: don't use cpu cycle API to get time The

[lng-odp] api-next broken?

2015-12-08 Thread Bill Fischofer
Trying to compile a fresh clone of api-next I'm seeing the following: CC odp_schedule.lo odp_schedule.c: In function 'schedule_loop': odp_schedule.c:589:13: error: storage size of 'next' isn't known odp_time_t next, wtime; ^ odp_schedule.c:589:19: error: storage size of