libmemif is compiled as part of per-patch verify jobs, including ubuntu 18.04 so must be something special in your setup. Can you paste your whole console log, starting with clean git checkout to pastebin?
— Damjan > On Jun 3, 2019, at 4:17 PM, Rafał Krych <[email protected]> wrote: > > Hello, > > I think it is not the same issue as the one reported in this ticket: > https://jira.fd.io/browse/VPP-1244 > > I'm doing some kind of research project for my company (evaluating libmemif > performance). Unfortunately since GLIBC 2.27 introduction (Ubuntu 18.04) my > test program fails to build with such message if libmemif library is included: > > In file included from libmemif/socket.h:21, > from libmemif/main.c:55: > libmemif/memif_private.h:231:1: error: static declaration of 'memfd_create' > follows non-static declaration > memfd_create (const char *name, unsigned int flags) > ^~~~~~~~~~~~ > In file included from /usr/include/x86_64-linux-gnu/bits/mman-linux.h:117, > from /usr/include/x86_64-linux-gnu/bits/mman.h:49, > from /usr/include/x86_64-linux-gnu/sys/mman.h:41, > from libmemif/main.c:27: > /usr/include/x86_64-linux-gnu/bits/mman-shared.h:46:5: note: previous > declaration of 'memfd_create' was here > int memfd_create (const char *__name, unsigned int __flags) __THROW; > ^~~~~~~~~~~~ > In file included from libmemif/socket.h:21, > from libmemif/socket.c:33: > libmemif/memif_private.h:231:1: error: static declaration of 'memfd_create' > follows non-static declaration > memfd_create (const char *name, unsigned int flags) > ^~~~~~~~~~~~ > In file included from /usr/include/x86_64-linux-gnu/bits/mman-linux.h:117, > from /usr/include/x86_64-linux-gnu/bits/mman.h:49, > from /usr/include/x86_64-linux-gnu/sys/mman.h:41, > from libmemif/socket.c:28: > /usr/include/x86_64-linux-gnu/bits/mman-shared.h:46:5: note: previous > declaration of 'memfd_create' was here > int memfd_create (const char *__name, unsigned int __flags) __THROW; > > I'm using most recent VPP version for this (commit > 365e724ffe5c5420b338b20c06a6c73171f39bce). > > It seems to be the same error as this one: > https://patchwork.openembedded.org/patch/147682/ > > Any chance to get this bug resolved in VPP? How I can help with this? > > BR, > Rafal > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#13252): https://lists.fd.io/g/vpp-dev/message/13252 > Mute This Topic: https://lists.fd.io/mt/32015500/675642 > Group Owner: [email protected] > Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]] > -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13257): https://lists.fd.io/g/vpp-dev/message/13257 Mute This Topic: https://lists.fd.io/mt/32015500/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
