From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5173CC32792 for ; Thu, 3 Oct 2019 06:28:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 28F32222C4 for ; Thu, 3 Oct 2019 06:28:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="QFdYmEH9" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726165AbfJCG21 (ORCPT ); Thu, 3 Oct 2019 02:28:27 -0400 Received: from mail-qt1-f196.google.com ([209.85.160.196]:36421 "EHLO mail-qt1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725827AbfJCG21 (ORCPT ); Thu, 3 Oct 2019 02:28:27 -0400 Received: by mail-qt1-f196.google.com with SMTP id o12so2090484qtf.3; Wed, 02 Oct 2019 23:28:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=dgpU7h9PioQW3CizRRaaufetm3YcqCHPVa7SstLyeu4=; b=QFdYmEH9dLqwAW9/I4SEPQx3lC0CfSY7dqPcbeO7+nYIj3TXlYZPdoIJHT4CSYgb4r vHVN40f8grBFb3bxJsx24MzMr//M46ho6dggrSicn53UsHqjDHUpyXURQoUxQwfShAUq ScC/vOBQdw5tqGGtPSLzufEYAcrOLq35/so3ZFeOJPNjKCRooIDB3Exj0wyGQKuxvOWh 39AA5xIpL8njnStqveYTDOlLVQ2RST8KIm1U2rkLWdeUHyuCZsuw7YPqH0lv7vj8EJ5E W/CKZZStdSjr/qXCDjs0CVt3FVTueEiOSi2tmlD8uBLgSGuMsG+EtaiN+uLplX2ZiFs9 Ke6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=dgpU7h9PioQW3CizRRaaufetm3YcqCHPVa7SstLyeu4=; b=jbVG3LjWjI87PJ872sPAECtpgXlOaLk39eY+B8/VuAidqib4GD6842ptfh/NgIN2za 6Mk53J6oM93baluLCN102dWP9r3reXpFBsUTUbauO4dSVUN4oLZa3YNcd9qf/Zu8cjD+ cnhi5HIibDpt4IFxUvrBMfYVsyLU8vg8Mo6Yo7rQBLdtJ1KvacdLcatu/xibFoQrMXpd 0i0FTitdyqef9DQAZ4l2O47cVjbXgj9jgVh+rUMgo9cwaPannrKkHJSXruC2YMujCSSG HbsY+DuPp8gsXaKVApjklLE4FqrYMKgvFSirxAw7KHnd9gMkVLSk6d65Drr11T1dVTEG 7PPg== X-Gm-Message-State: APjAAAVe9jKEYhywO9dABZd1JhhM4OznGjYwjIab0IEBeLRPjowq8Ezt Oxor0bbSYOT3w6vVjJaiImxACZc/35NfumSWAIGmrBntH60WrQ== X-Google-Smtp-Source: APXvYqysVuWAtPazJUsDrDS0BrXrwv3wVkdZJfligraFHUVD6BGj/+KQq/1DWWkwZJfvbeCIOa15+hYIBckJc7eu994= X-Received: by 2002:ac8:3061:: with SMTP id g30mr8376963qte.46.1570084105800; Wed, 02 Oct 2019 23:28:25 -0700 (PDT) MIME-Version: 1.0 References: <20191001101429.24965-1-bjorn.topel@gmail.com> <20191002231448.GA10649@khorivan> In-Reply-To: <20191002231448.GA10649@khorivan> From: =?UTF-8?B?QmrDtnJuIFTDtnBlbA==?= Date: Thu, 3 Oct 2019 08:28:14 +0200 Message-ID: Subject: Re: [PATCH bpf] samples/bpf: kbuild: add CONFIG_SAMPLE_BPF Kconfig To: Ivan Khoronzhuk Cc: Masahiro Yamada , Networking , Alexei Starovoitov , Daniel Borkmann , =?UTF-8?B?QmrDtnJuIFTDtnBlbA==?= , Linux Kbuild mailing list , bpf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Thu, 3 Oct 2019 at 01:14, Ivan Khoronzhuk w= rote: > > On Wed, Oct 02, 2019 at 09:41:15AM +0200, Bj=C3=B6rn T=C3=B6pel wrote: > >On Wed, 2 Oct 2019 at 03:49, Masahiro Yamada > > wrote: > >> > >[...] > >> > Yes, the BPF samples require clang/LLVM with BPF support to build. A= ny > >> > suggestion on a good way to address this (missing tools), better tha= n > >> > the warning above? After the commit 394053f4a4b3 ("kbuild: make sing= le > >> > targets work more correctly"), it's no longer possible to build > >> > samples/bpf without support in the samples/Makefile. > >> > >> > >> You can with > >> > >> "make M=3Dsamples/bpf" > >> > > > >Oh, I didn't know that. Does M=3D support "output" builds (O=3D)? > > > >I usually just build samples/bpf/ with: > > > > $ make V=3D1 O=3D/home/foo/build/bleh samples/bpf/ > > > > > >Bj=C3=B6rn > > Shouldn't README be updated? > Hmm, the M=3D variant doesn't work at all for me. The build is still broken for me. Maybe I'm missing anything obvious... > -- > Regards, > Ivan Khoronzhuk