[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14b99d26a4cff1c813c92818dc1234007fa06fc9.camel@oracle.com>
Date: Tue, 13 Aug 2019 18:19:01 +0200
From: Knut Omang <knut.omang@...cle.com>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: "open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Shuah Khan <shuah@...nel.org>,
Jonathan Corbet <corbet@....net>,
Michal Marek <michal.lkml@...kovi.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Shreyans Devendra Doshi <0xinfosect0r@...il.com>,
Alan Maguire <alan.maguire@...cle.com>,
Brendan Higgins <brendanhiggins@...gle.com>,
Kevin Hilman <khilman@...libre.com>,
Hidenori Yamaji <hidenori.yamaji@...y.com>,
Frank Rowand <frowand.list@...il.com>,
Timothy Bird <Tim.Bird@...y.com>,
Luis Chamberlain <mcgrof@...nel.org>,
"Theodore Ts'o" <tytso@....edu>, Daniel Vetter <daniel@...ll.ch>,
Stephen Boyd <sboyd@...nel.org>
Subject: Re: [RFC 01/19] kbuild: Fixes to rules for host-cshlib and
host-cxxshlib
On Tue, 2019-08-13 at 23:01 +0900, Masahiro Yamada wrote:
> On Tue, Aug 13, 2019 at 3:13 PM Knut Omang <knut.omang@...cle.com> wrote:
> >
> > C++ libraries interfacing to C APIs might sometimes need some glue
> > logic more easily written in C.
> > Allow a C++ library to also contain 0 or more C objects.
> >
> > Also fix rules for both C and C++ shared libraries:
> > - C++ shared libraries depended on .c instead of .cc files
> > - Rules were referenced as -objs instead of the intended
> > -cobjs and -cxxobjs following the pattern from hostprogs*.
> >
> > Signed-off-by: Knut Omang <knut.omang@...cle.com>
>
>
> How is this patch related to the rest of this series?
This is just my (likely naive) way I to get what I had working
using autotools in the Github version of KTF) translated into something
comparable using kbuild only. We need to build a shared library consisting
of a few C++ files and a very simple C file, and a couple of simple binaries,
and the rule in there does seem to take .c files and subject them to the
C++ compiler, which makes this difficult to achieve?
> This patch breaks GCC-plugins.
> Did you really compile-test this patch before the submission?
Sorry for my ignorance here:
I ran through the kernel build and installed the resulting kernel
on a VM that I used to test this, if that's what you are asking
about?
Do I need some unusual .config options or run a special make target
to trigger the problem you see?
I used a recent Fedora config with default values for new options,
and ran the normal default make target (also with O=) and make selftests
to test the patch itself.
Thanks,
Knut
> --
> Best Regards
>
> Masahiro Yamada
Powered by blists - more mailing lists