lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 17 Sep 2019 13:14:06 +0300 From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com> To: Ivan Khoronzhuk <ivan.khoronzhuk@...aro.org>, ast@...nel.org, daniel@...earbox.net, yhs@...com, davem@...emloft.net, jakub.kicinski@...ronome.com, hawk@...nel.org, john.fastabend@...il.com Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org, bpf@...r.kernel.org, clang-built-linux@...glegroups.com Subject: Re: [PATCH v3 bpf-next 09/14] samples: bpf: makefile: use own flags but not host when cross compile Hello! On 16.09.2019 13:54, Ivan Khoronzhuk wrote: > While compile natively, the hosts cflags and ldflags are equal to ones Compiling. Host's. > used from HOSTCFLAGS and HOSTLDFLAGS. When cross compiling it should > have own, used for target arch. While verification, for arm, arm64 and > x86_64 the following flags were used alsways: > > -Wall > -O2 > -fomit-frame-pointer > -Wmissing-prototypes > -Wstrict-prototypes > > So, add them as they were verified and used before adding > Makefile.target, but anyway limit it only for cross compile options as > for host can be some configurations when another options can be used, > So, for host arch samples left all as is, it allows to avoid potential > option mistmatches for existent environments. Mismatches. > Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@...aro.org> [...] MBR, Sergei
Powered by blists - more mailing lists