From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] eal: fix build issue Date: Tue, 06 Nov 2018 13:29:19 +0100 Message-ID: <3520386.84pXejHKmD@xps> References: <20181106114435.14770-1-jerin.jacob@caviumnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" , "Jacob, Jerin" , "stable@dpdk.org" To: Jerin Jacob Return-path: In-Reply-To: <20181106114435.14770-1-jerin.jacob@caviumnetworks.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 06/11/2018 12:45, Jerin Jacob: > Some toolchain has fls() definition in string.h as argument type int, > which is conflicting uint32_t argument type. >=20 > /export/dpdk.org/lib/librte_eal/common/rte_reciprocal.c:47:19: > error: conflicting types for =E2=80=98fls=E2=80=99 > static inline int fls(uint32_t x) > ^~~ >=20 > /opt/marvell-tools-201/aarch64-marvell-elf/include/strings.h:59:6: > note: previous declaration of =E2=80=98fls=E2=80=99 was here > int fls(int) __pure2; >=20 > FreeBSD string.h also has fls() with argument as int type. > https://www.freebsd.org/cgi/man.cgi?query=3Dfls&sektion=3D3 >=20 > Fixing the conflict by renaming internal function as __fls Why not rte_fls? Would it be more future proof?