Re: [vpp-dev] 18.04 RC2 this Wednesday!

2018-04-10 Thread Chris Luke 
Thanks for the reports. Thankfully they can be safely ignored.

The first one is a collection of warnings generated by the DPDK build step; 
they relate to a compiler hint that a function does not return and the specific 
C variant doesn't support it; it's harmless for now, but probably should be 
looked at since it suggests DPDK is using C primitives from a C version 
different from that we're compiling, or similar.

The second is just notices that some .api files have not yet updated how they 
deal with variable sized arrays; still supported, though perhaps for the next 
release we should consider cleaning those up.

Chris.

From: vpp-dev@lists.fd.io  On Behalf Of Jan Hugo Prins | 
BetterBe
Sent: Tuesday, April 10, 2018 4:25
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] 18.04 RC2 this Wednesday!

The following error scrolls by a lot during compile:

default: gcc -std=gnu99 -c -g -O3 -fwrapv -U__STRICT_ANSI__ -fno-common 
-Werror=attributes -W -Wall -pedantic -Wno-long-long -Werror=implicit 
-Werror=missing-braces -Werror=return-type -Werror=trigraphs 
-Werror=pointer-arith -Werror=missing-prototypes -Werror=missing-declarations 
-Werror=comment -Werror=vla -DHAVE_CONFIG_H -I. -I. -I./include -I./include 
-I./x86 -I./x86 -I./asm -I./asm -I./disasm -I./disasm -I./output -I./output -o 
rdoff/rdlib.o rdoff/rdlib.c
default: In file included from rdoff/rdfutils.h:44:0,
default:  from rdoff/rdoff.c:50:
default: ./include/nasmlib.h:113:11: warning: ISO C99 does not support 
'_Noreturn' [-Wpedantic]
default:  no_return nasm_assert_failed(const char *, int, const char *);
default:^
default: In file included from rdoff/rdfutils.h:45:0,
default:  from rdoff/rdoff.c:50:
default: ./include/error.h:47:29: warning: ISO C99 does not support 
'_Noreturn' [-Wpedantic]
default:  no_return printf_func(2, 3) nasm_fatal(int flags, const char 
*fmt, ...);
default:  ^
default: ./include/error.h:48:29: warning: ISO C99 does not support 
'_Noreturn' [-Wpedantic]
default:  no_return printf_func(2, 3) nasm_panic(int flags, const char 
*fmt, ...);
default:  ^
default: ./include/error.h:49:11: warning: ISO C99 does not support 
'_Noreturn' [-Wpedantic]
default:  no_return nasm_panic_from_macro(const char *file, int line);
default:^
default: In file included from rdoff/rdfutils.h:44:0,
default:  from rdoff/rdfload.h:15,
default:  from rdoff/rdfload.c:51:
default: ./include/nasmlib.h:113:11: warning: ISO C99 does not support 
'_Noreturn' [-Wpedantic]
default:  no_return nasm_assert_failed(const char *, int, const char *);
default:^
default: In file included from rdoff/rdfutils.h:45:0,
default:  from rdoff/rdfload.h:15,
default:  from rdoff/rdfload.c:51:
default: ./include/error.h:47:29: warning: ISO C99 does not support 
'_Noreturn' [-Wpedantic]
default:  no_return printf_func(2, 3) nasm_fatal(int flags, const char 
*fmt, ...);
default:  ^
default: ./include/error.h:48:29: warning: ISO C99 does not support 
'_Noreturn' [-Wpedantic]
default:  no_return printf_func(2, 3) nasm_panic(int flags, const char 
*fmt, ...);
default:  ^
default: ./include/error.h:49:11: warning: ISO C99 does not support 
'_Noreturn' [-Wpedantic]
default:  no_return nasm_panic_from_macro(const char *file, int line);
default:^


And the following:


default: make[4]: Entering directory 
`/vpp/build-root/rpmbuild/vpp-18.07/build-root/build-vpp-native/vpp'
default:   APIGEN   vlibmemory/memclnt.api.h
default:   JSON API vlibmemory/memclnt.api.json
default: 
WARNING:vppapigen:/vpp/build-root/rpmbuild/vpp-18.07/build-data/../src/vlibmemory/memclnt.api:0:1:
 Old Style VLA: u8 data[0];
default: 
WARNING:vppapigen:/vpp/build-root/rpmbuild/vpp-18.07/build-data/../src/vlibmemory/memclnt.api:0:1:
 Old Style VLA: u8 data[0];


No idea if it is anywhere critical or if someone has created reports for this 
in the past.

Jan Hugo


On 04/09/2018 08:43 PM, Chris Luke wrote:
All,

Gentle reminder that 18.04 RC2 will be posted on Wednesday.

Note: After Wednesday's RC2 Milestone, only critical bug fixes will be merged 
into branch stable/1804.  Please review open anomalies for candidates to be 
fixed this week. Also, please remember to open a Jira ticket for all patches 
submitted to stable branches.

Cheers,
Chris.

--
Kind regards

Jan Hugo Prins
DevOps Engineer

[cid:image001.png@01D3D09A.F7F6E450]<https://betterbe.com>

Auke Vleerstraat 140 E
7547 AN Enschede
CC no. 
08097527<https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=08097527>

T

Re: [vpp-dev] 18.04 RC2 this Wednesday!

2018-04-10 Thread Jan Hugo Prins | BetterBe 
The following error scrolls by a lot during compile:

    default: gcc -std=gnu99 -c -g -O3 -fwrapv -U__STRICT_ANSI__
-fno-common -Werror=attributes -W -Wall -pedantic -Wno-long-long
-Werror=implicit -Werror=missing-braces -Werror=return-type
-Werror=trigraphs -Werror=pointer-arith -Werror=missing-prototypes
-Werror=missing-declarations -Werror=comment -Werror=vla -DHAVE_CONFIG_H
-I. -I. -I./include -I./include -I./x86 -I./x86 -I./asm -I./asm
-I./disasm -I./disasm -I./output -I./output -o rdoff/rdlib.o rdoff/rdlib.c
    default: In file included from rdoff/rdfutils.h:44:0,
    default:  from rdoff/rdoff.c:50:
    default: ./include/nasmlib.h:113:11: warning: ISO C99 does not
support '_Noreturn' [-Wpedantic]
    default:  no_return nasm_assert_failed(const char *, int, const char *);
    default:    ^
    default: In file included from rdoff/rdfutils.h:45:0,
    default:  from rdoff/rdoff.c:50:
    default: ./include/error.h:47:29: warning: ISO C99 does not support
'_Noreturn' [-Wpedantic]
    default:  no_return printf_func(2, 3) nasm_fatal(int flags, const
char *fmt, ...);
    default:  ^
    default: ./include/error.h:48:29: warning: ISO C99 does not support
'_Noreturn' [-Wpedantic]
    default:  no_return printf_func(2, 3) nasm_panic(int flags, const
char *fmt, ...);
    default:  ^
    default: ./include/error.h:49:11: warning: ISO C99 does not support
'_Noreturn' [-Wpedantic]
    default:  no_return nasm_panic_from_macro(const char *file, int line);
    default:    ^
    default: In file included from rdoff/rdfutils.h:44:0,
    default:  from rdoff/rdfload.h:15,
    default:  from rdoff/rdfload.c:51:
    default: ./include/nasmlib.h:113:11: warning: ISO C99 does not
support '_Noreturn' [-Wpedantic]
    default:  no_return nasm_assert_failed(const char *, int, const char *);
    default:    ^
    default: In file included from rdoff/rdfutils.h:45:0,
    default:  from rdoff/rdfload.h:15,
    default:  from rdoff/rdfload.c:51:
    default: ./include/error.h:47:29: warning: ISO C99 does not support
'_Noreturn' [-Wpedantic]
    default:  no_return printf_func(2, 3) nasm_fatal(int flags, const
char *fmt, ...);
    default:  ^
    default: ./include/error.h:48:29: warning: ISO C99 does not support
'_Noreturn' [-Wpedantic]
    default:  no_return printf_func(2, 3) nasm_panic(int flags, const
char *fmt, ...);
    default:  ^
    default: ./include/error.h:49:11: warning: ISO C99 does not support
'_Noreturn' [-Wpedantic]
    default:  no_return nasm_panic_from_macro(const char *file, int line);
    default:    ^


And the following:


    default: make[4]: Entering directory
`/vpp/build-root/rpmbuild/vpp-18.07/build-root/build-vpp-native/vpp'
    default:   APIGEN   vlibmemory/memclnt.api.h
    default:   JSON API vlibmemory/memclnt.api.json
    default:
WARNING:vppapigen:/vpp/build-root/rpmbuild/vpp-18.07/build-data/../src/vlibmemory/memclnt.api:0:1:
Old Style VLA: u8 data[0];
    default:
WARNING:vppapigen:/vpp/build-root/rpmbuild/vpp-18.07/build-data/../src/vlibmemory/memclnt.api:0:1:
Old Style VLA: u8 data[0];


No idea if it is anywhere critical or if someone has created reports for
this in the past.

Jan Hugo



On 04/09/2018 08:43 PM, Chris Luke wrote:
>
> All,
>
>  
>
> Gentle reminder that 18.04 RC2 will be posted on Wednesday.
>
>  
>
> Note: After Wednesday's RC2 Milestone, only critical bug fixes will be
> merged into branch stable/1804.  Please review open anomalies for
> candidates to be fixed this week. Also, please remember to open a Jira
> ticket for all patches submitted to stable branches.
>
>  
>
> Cheers,
>
> Chris.
>
> 

-- 
Kind regards

Jan Hugo Prins
/DevOps Engineer/

Auke Vleerstraat 140 E
7547 AN Enschede
CC no. 08097527

*T* +31 (0) 53 48 00 694 
*E* jpr...@betterbe.com 
*M* +31 (0)6 263 58 951 
www.betterbe.com 
BetterBe accepts no liability for the content of this email, or for the
consequences of any actions taken on the basis
of the information provided, unless that information is subsequently
confirmed in writing. If you are not the intended
recipient you are notified that disclosing, copying, distributing or
taking any action in reliance on the contents of this
information is strictly prohibited.

Re: [vpp-dev] 18.04 RC2 this Wednesday!

2018-04-10 Thread Jan Hugo Prins | BetterBe 
I understand completely.
Is the maintainer of these plugins here on the mailinglist?

Jan Hugo

On 04/09/2018 11:21 PM, Chris Luke wrote:
>
> Unfortunately it’s too late for such large features to be merged with
> VPP’s stable branch, which is now focused on bug fixes.
>
>  
>
> Additionally, it’s up to the maintainers of those plugins to propose
> merging their work with the VPP project.
>
>  
>
> Cheers,
>
> Chris.
>
>  
>
>  
>
>  
>
> *From:*vpp-dev@lists.fd.io  *On Behalf Of *Jan
> Hugo Prins | BetterBe
> *Sent:* Monday, April 9, 2018 17:15
> *To:* vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] 18.04 RC2 this Wednesday!
>
>  
>
> Hello,
>
> Would it be possible to get the router and netlink plugin, that are
> currently in the VPPSB project, merged into 18.04 ?
> I would like to work with them building a set of routers, and having
> them in the stable branche would mean that the chance of some patches
> breaking this functionality would be a lot smaller.
>
> Cheers,
> Jan Hugo Prins
>
> On 04/09/2018 08:43 PM, Chris Luke wrote:
>
> All,
>
>  
>
> Gentle reminder that 18.04 RC2 will be posted on Wednesday.
>
>  
>
> Note: After Wednesday's RC2 Milestone, only critical bug fixes
> will be merged into branch stable/1804.  Please review open
> anomalies for candidates to be fixed this week. Also, please
> remember to open a Jira ticket for all patches submitted to stable
> branches.
>
>  
>
> Cheers,
>
> Chris.
>
>  
>
> -- 
>
> Kind regards
>
> Jan Hugo Prins
> /DevOps Engineer/
>
> <https://betterbe.com>
>
> Auke Vleerstraat 140 E
> 7547 AN Enschede
> CC no. 08097527
> <https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=08097527>
>
>   
>
> *T*+31 (0) 53 48 00 694 
> *E* jpr...@betterbe.com <mailto:jpr...@betterbe.com>
> *M* +31 (0)6 263 58 951 
>
>   
>
> *www.betterbe.com* <https://www.betterbe.com>
>
> BetterBe accepts no liability for the content of this email, or for
> the consequences of any actions taken on the basis
> of the information provided, unless that information is subsequently
> confirmed in writing. If you are not the intended
> recipient you are notified that disclosing, copying, distributing or
> taking any action in reliance on the contents of this
> information is strictly prohibited.
>
> 

-- 
Kind regards

Jan Hugo Prins
/DevOps Engineer/
<https://betterbe.com>
Auke Vleerstraat 140 E
7547 AN Enschede
CC no. 08097527
<https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=08097527>
*T* +31 (0) 53 48 00 694 
*E* jpr...@betterbe.com <mailto:jpr...@betterbe.com>
*M* +31 (0)6 263 58 951 
www.betterbe.com <https://www.betterbe.com>
BetterBe accepts no liability for the content of this email, or for the
consequences of any actions taken on the basis
of the information provided, unless that information is subsequently
confirmed in writing. If you are not the intended
recipient you are notified that disclosing, copying, distributing or
taking any action in reliance on the contents of this
information is strictly prohibited.

Re: [vpp-dev] 18.04 RC2 this Wednesday!

2018-04-09 Thread Dave Barach 
+1, not practical at this time… Dave

From:  on behalf of Chris Luke 
Date: Monday, April 9, 2018 at 2:21 PM
To: "vpp-dev@lists.fd.io" 
Subject: Re: [vpp-dev] 18.04 RC2 this Wednesday!

Unfortunately it’s too late for such large features to be merged with VPP’s 
stable branch, which is now focused on bug fixes.

Additionally, it’s up to the maintainers of those plugins to propose merging 
their work with the VPP project.

Cheers,
Chris.



From: vpp-dev@lists.fd.io  On Behalf Of Jan Hugo Prins | 
BetterBe
Sent: Monday, April 9, 2018 17:15
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] 18.04 RC2 this Wednesday!

Hello,

Would it be possible to get the router and netlink plugin, that are currently 
in the VPPSB project, merged into 18.04 ?
I would like to work with them building a set of routers, and having them in 
the stable branche would mean that the chance of some patches breaking this 
functionality would be a lot smaller.

Cheers,
Jan Hugo Prins


On 04/09/2018 08:43 PM, Chris Luke wrote:
All,

Gentle reminder that 18.04 RC2 will be posted on Wednesday.

Note: After Wednesday's RC2 Milestone, only critical bug fixes will be merged 
into branch stable/1804.  Please review open anomalies for candidates to be 
fixed this week. Also, please remember to open a Jira ticket for all patches 
submitted to stable branches.

Cheers,
Chris.

--
Kind regards

Jan Hugo Prins
DevOps Engineer

[cid:image001.png@01D3D023.56DAF7E0]<https://betterbe.com>

Auke Vleerstraat 140 E
7547 AN Enschede
CC no. 
08097527<https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=08097527>

T +31 (0) 53 48 00 694
E jpr...@betterbe.com<mailto:jpr...@betterbe.com>
M +31 (0)6 263 58 951

www.betterbe.com<https://www.betterbe.com>

BetterBe accepts no liability for the content of this email, or for the 
consequences of any actions taken on the basis
of the information provided, unless that information is subsequently confirmed 
in writing. If you are not the intended
recipient you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this
information is strictly prohibited.

Re: [vpp-dev] 18.04 RC2 this Wednesday!

2018-04-09 Thread Chris Luke 
Unfortunately it's too late for such large features to be merged with VPP's 
stable branch, which is now focused on bug fixes.

Additionally, it's up to the maintainers of those plugins to propose merging 
their work with the VPP project.

Cheers,
Chris.



From: vpp-dev@lists.fd.io  On Behalf Of Jan Hugo Prins | 
BetterBe
Sent: Monday, April 9, 2018 17:15
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] 18.04 RC2 this Wednesday!

Hello,

Would it be possible to get the router and netlink plugin, that are currently 
in the VPPSB project, merged into 18.04 ?
I would like to work with them building a set of routers, and having them in 
the stable branche would mean that the chance of some patches breaking this 
functionality would be a lot smaller.

Cheers,
Jan Hugo Prins

On 04/09/2018 08:43 PM, Chris Luke wrote:
All,

Gentle reminder that 18.04 RC2 will be posted on Wednesday.

Note: After Wednesday's RC2 Milestone, only critical bug fixes will be merged 
into branch stable/1804.  Please review open anomalies for candidates to be 
fixed this week. Also, please remember to open a Jira ticket for all patches 
submitted to stable branches.

Cheers,
Chris.

--
Kind regards

Jan Hugo Prins
DevOps Engineer

[cid:image001.png@01D3D027.222AD250]<https://betterbe.com>

Auke Vleerstraat 140 E
7547 AN Enschede
CC no. 
08097527<https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=08097527>

T +31 (0) 53 48 00 694
E jpr...@betterbe.com<mailto:jpr...@betterbe.com>
M +31 (0)6 263 58 951

www.betterbe.com<https://www.betterbe.com>

BetterBe accepts no liability for the content of this email, or for the 
consequences of any actions taken on the basis
of the information provided, unless that information is subsequently confirmed 
in writing. If you are not the intended
recipient you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this
information is strictly prohibited.

Re: [vpp-dev] 18.04 RC2 this Wednesday!

2018-04-09 Thread Jan Hugo Prins | BetterBe 
Hello,

Would it be possible to get the router and netlink plugin, that are
currently in the VPPSB project, merged into 18.04 ?
I would like to work with them building a set of routers, and having
them in the stable branche would mean that the chance of some patches
breaking this functionality would be a lot smaller.

Cheers,
Jan Hugo Prins


On 04/09/2018 08:43 PM, Chris Luke wrote:
>
> All,
>
>  
>
> Gentle reminder that 18.04 RC2 will be posted on Wednesday.
>
>  
>
> Note: After Wednesday's RC2 Milestone, only critical bug fixes will be
> merged into branch stable/1804.  Please review open anomalies for
> candidates to be fixed this week. Also, please remember to open a Jira
> ticket for all patches submitted to stable branches.
>
>  
>
> Cheers,
>
> Chris.
>
> 

-- 
Kind regards

Jan Hugo Prins
/DevOps Engineer/

Auke Vleerstraat 140 E
7547 AN Enschede
CC no. 08097527

*T* +31 (0) 53 48 00 694 
*E* jpr...@betterbe.com 
*M* +31 (0)6 263 58 951 
www.betterbe.com 
BetterBe accepts no liability for the content of this email, or for the
consequences of any actions taken on the basis
of the information provided, unless that information is subsequently
confirmed in writing. If you are not the intended
recipient you are notified that disclosing, copying, distributing or
taking any action in reliance on the contents of this
information is strictly prohibited.

[vpp-dev] 18.04 RC2 this Wednesday!

2018-04-09 Thread Chris Luke 
All,

Gentle reminder that 18.04 RC2 will be posted on Wednesday.

Note: After Wednesday's RC2 Milestone, only critical bug fixes will be merged 
into branch stable/1804.  Please review open anomalies for candidates to be 
fixed this week. Also, please remember to open a Jira ticket for all patches 
submitted to stable branches.

Cheers,
Chris.