Re: [vpp-dev] Build on Fedora 25 failed

On 01/17/2017 06:03 PM, Kevin Wilson wrote: Hi, Still build fails. After installing redhat-rpm-config, and again wiping out the vpp tree and cloning again from scratch, and running again the process from beginning, first /build-root/vagrant/build.sh which completed ok and then: cd build-root

Re: [vpp-dev] Build on Fedora 25 failed

I can tell you this, Kevin: if you do "make build-release" and follow that with your install-rpm command, you will see the exact same error that you are seeing. But if you follow "make build-release" with "make pkg-rpm" then the following stuff happens at the start, setting you up for install-rpm

Re: [vpp-dev] Weird VPP API message processing failure

On Tue, Jan 17, 2017 at 3:45 PM, Alexander Popovsky (apopovsk) < apopo...@cisco.com> wrote: > We have seen a similar issue related to the same ‘API refactoring : dpdk’ > change. > We are using an external API binding layer in C-language in our VPP based > solution. > After the change, it took

Re: [vpp-dev] Weird VPP API message processing failure

> We have seen a similar issue related to the same ‘API refactoring : dpdk’ > change. > We are using an external API binding layer in C-language in our VPP based > solution. > After the change, it took some digging to add –DDPDK=1 to get things back to > working. > > Looking forward, should it

Re: [vpp-dev] Weird VPP API message processing failure

We have seen a similar issue related to the same ‘API refactoring : dpdk’ change. We are using an external API binding layer in C-language in our VPP based solution. After the change, it took some digging to add –DDPDK=1 to get things back to working. Looking forward, should it be considered a

Re: [vpp-dev] Build on Fedora 25 failed

I tried a variation, and I had success: One thing, I didn't do the dependencies install, I just waited until crashes and then looked to see what my system was missing. For my second step, I needed to add ganglia-devel and chrpath packages. My second step is "make pkg-rpm" from the top level

Re: [vpp-dev] Build on Fedora 25 failed

Hi, Well, there is some progress as the first step succeeds now, but the second step fail. In more details: Just tried now wiping whole the vpp tree, cloning it again, and running: ./build-root/vagrant/build.sh And it completed ok. Then went to the second step according the the

Re: [vpp-dev] show interface address with multiple tables

Hi Dave, Billy, I’ve no objection to VPP rejecting the change of table mapping when IPv[46] configurations exist. I’ll make the change as time permits, unless some-one else beats me to it ☺ And update the documentation accordingly. Regards, neale From: Billy McFall Date:

Re: [vpp-dev] Weird VPP API message processing failure

On Mon, Jan 16, 2017 at 6:33 PM, Jon Loeliger wrote: > Folks, > > We are seeing a really strange VPP API message processing problem. > The scenario goes like this... > > > I've started to isolate it with git bisect, and so far I believe the > behavior changed between these

Re: [vpp-dev] Build on Fedora 25 failed

I see another possible issue for Ed in the Makefile, if Fedora 25 is to be supported: zlib seems to be hardcoded to a level that is earlier than Fedora 25. Kevin can you make certain you have it on your system. Your log mentioned zlib. Just by chance, on my Fedora, I have libtool-ltdl in additon

Re: [vpp-dev] Build on Fedora 25 failed

Thanks to Burt, Connoly and Billy. Still, after: dnf group install 'C Development Tools and Libraries' and running again: ./build-root/vagrant/build.sh I get: " line 2212: LT_INIT: command not found" ... See full log following immediately. I googled for this error, some said it it related to

Re: [vpp-dev] show interface address with multiple tables

By a tag, you mean an element like @todo that both renders the paragraph such that it stands out and also produces a list (index) of all such items? That is fairly straightforward. There is some limited functionality for this built in to Doxygen[1], and separately I wrote a pre-Doxygen-parser

Re: [vpp-dev] [csit-dev] crypto-dev support/libraries

All, Many thanks to vpp-dev team for helping us to drive this situation to a clear conclusion on a VPP project call just now. Special thanks to Damjan, who took initiative, followed up, and checked with LF FD.io team and Ed regarding options to deal with export-restricted crypto

Re: [vpp-dev] show interface address with multiple tables

Billy, Thanks for pointing out that this particular case is documented in doxygen. I didn't follow up on this specific example but was highlighting the general issue. It would be nice to have specific tag in Doxygen which identifies configuration constraint definitions. Thanks, -daw- On

Re: [vpp-dev] show interface address with multiple tables

Dave, I agree with your statements about VPP probably needs to add the verification. I wanted to add that this constraint was added to the Doxygen documentation. But there are a lot of constraints that are not documented, and if they are, I'm not sure how to better propagate the information to

Re: [vpp-dev] Build on Fedora 25 failed

Aha, if one wishes to use a dnf group for pulling in autoconf, the correct group name is 'C Development Tools and Libraries'. So this plus what you found, Padraig, should be fixed. Burt On Tue, Jan 17, 2017 at 9:45 AM, Connolly, Padraig < padraig.conno...@intel.com> wrote: > Yes, also autoconf

Re: [vpp-dev] Build on Fedora 25 failed

Yes, also autoconf seems to be repeated twice in DEB_DEPENDS Thanks, Padraig From: Burt Silverman [mailto:bur...@gmail.com] Sent: Tuesday, January 17, 2017 2:39 PM To: Connolly, Padraig Cc: Edward Warnicke ; vpp-dev@lists.fd.io Subject: Re:

Re: [vpp-dev] show interface address with multiple tables

Neale, Given this constraint, IMO it should be verified prior to enacting the change of the interface table and the request should be rejected if the constraint is not met. The $64,000 question is whether this constraint should be verified by VPP itself or the management agent. Prior to

Re: [vpp-dev] Build on Fedora 25 failed

I do not understand why it is not there, myself. I looked at the RPM_DEPENDS_GROUP, the dnf group 'Development Tools', but autoconf is not part of that. So there are no tricks involved. Looks like Ed Warnicke set this stuff up. Perhaps he can get it into sync with the DEB/Ubuntu case. Burt On

Re: [vpp-dev] VPP-556 - vpp crashing in an openstack odl stack

Hi Dave, John, I've tried building the latest 17.01 vpp (using "make V=0 PLATFORM=vpp TAG=vpp_debug install-rpm" - I understand that's where the TAG=vpp_debug is refereing to) and the issue is no longer present there, but there is something else - now vpp crashes when I delete a vhost-user

Re: [vpp-dev] Coverity warnings in generated java files

Hi, It looks like coverity is applied to debug build, could you please to update path to use build-vpp_debug-native ? Thanks, Marek From: Luke, Chris [mailto:chris_l...@comcast.com] Sent: 12 stycznia 2017 14:54 To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)

[vpp-dev] Help regarding VPP build with ODP

Hi All, I am working on VPP/ODP integration. I had made some changes earlier in the Makefiles(vnet.mk,vpp.mk) to build ODP with VPP. Below are the changes I made for ODP: 1) I had copied the ODP includes,bin and library to VPP installed path (vpp/build-root/install-vpp). 2) And added ODP

Re: [vpp-dev] Weird VPP API message processing failure

Hi Jon, > We are seeing a really strange VPP API message processing problem. > The scenario goes like this... > > Our CLI issues C API calls through the vlib API. The messages hit > the shared memory queue, but are not processed. They sit there. Is it VPP that does not process the messages or

Re: [vpp-dev] [csit-dev] sporadically failing functional tests: L2BD and VXLANoIPv4oVLAN

I'll fix the test cases. From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Damjan Marion (damarion) Sent: 16. januára 2017 22:39 To: csit-...@lists.fd.io Cc: vpp-dev Subject: Re: [vpp-dev] [csit-dev] sporadically failing functional tests: