From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Borkmann Subject: Re: [PATCH bpf-next v3] libbpf: make sure bpf headers are c++ include-able Date: Wed, 21 Nov 2018 23:17:15 +0100 Message-ID: <602721fa-4841-e4da-18e1-29ba4c5962c3@iogearbox.net> References: <20181121172944.146320-1-sdf@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: yhs@fb.com To: Stanislav Fomichev , netdev@vger.kernel.org, ast@kernel.org Return-path: Received: from www62.your-server.de ([213.133.104.62]:41450 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731864AbeKVIxd (ORCPT ); Thu, 22 Nov 2018 03:53:33 -0500 In-Reply-To: <20181121172944.146320-1-sdf@google.com> Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: On 11/21/2018 06:29 PM, Stanislav Fomichev wrote: > Wrap headers in extern "C", to turn off C++ mangling. > This simplifies including libbpf in c++ and linking against it. > > v2 changes: > * do the same for btf.h > > v3 changes: > * test_libbpf.cpp to test for possible future c++ breakages > > Signed-off-by: Stanislav Fomichev Applied, thanks!