[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160503232932.706dd3bb081df5d04a390de9@gmail.com>
Date: Tue, 3 May 2016 23:29:32 +0200
From: Emese Revfy <re.emese@...il.com>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>, PaX Team
<pageexec@...email.hu>, Brad Spengler <spender@...ecurity.net>,
kernel-hardening@...ts.openwall.com, Michal Marek <mmarek@...e.com>, Kees
Cook <keescook@...omium.org>, Rasmus Villemoes <linux@...musvillemoes.dk>,
Fengguang Wu <fengguang.wu@...el.com>, Dmitry Vyukov <dvyukov@...gle.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, David Brown
<david.brown@...aro.org>
Subject: Re: [PATCH v7 1/6] Shared library support
On Tue, 3 May 2016 11:00:56 +0900
Masahiro Yamada <yamada.masahiro@...ionext.com> wrote:
Hi,
> # Compile .c file, create position independent .o file
> # host-cxxshobjs -> .o
> quiet_cmd_host-cxxshobjs = HOSTCXX -fPIC $@
> cmd_host-cxxshobjs = $(HOSTCXX) $(hostcxx_flags) -fPIC -c -o $@ $<
> $(host-cxxshobjs): $(obj)/%.o: $(src)/%.c FORCE
> $(call if_changed_dep,host-cxxshobjs)
>
>
>
>
> We generally use HOSTCC to compile *.c files,
> and HOSTCXX to compile *.cc files.
>
>
> But, here, you mention to use HOSTCXX to compile .c files
> such as cyc_complexity_plugin.c, sancov_plugin.c, etc.
>
> This is not straight-forward. It is worthwhile to comment the reason.
I wrote a comment about it here:
https://github.com/ephox-gcc-plugins/gcc-plugins_linux-next/commit/74f6343a7f13c071e00c417332051e25f15009ea
--
Emese
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
