Hi Marcin, > > Hi Akhil, > I've double checked and there is no problem with linking application against > shared libraries, because inline functions are being inlined during > compilation > and before linking is done. To be more specific: there is not such symbol as > rte_ipv6_get_next_ext in ipsec-secgw.o (which uses this function in > prepare_one_packet function). > > There are a number of inline experimental functions defined today and they > are > mostly (43 out of 59) not listed in maps, e.g. rte_ticketlock functions family > defined here: > lib/librte_eal/common/include/generic/rte_ticketlock.h > > Is there any particular reason we should put inlines in maps? Maps are used by > linker to control versions of shared libraries and inlines are not processed > by > linker. > > I am aware this patchset causes build failures on BSDs - this is a > project-wide > issue which I have addressed here: > http://patchwork.dpdk.org/patch/53406/ > I'll put a note in the next version of this patchset's cover that it depends > on > abovementioned patchset. > > Marcin
Thanks for correcting me.
