[lttng-dev] Babeltrace2 - compilation error with intel18
dunlap at ucar.edu
Mon Mar 23 12:05:07 EDT 2020
Yes, I will be happy to give this a try. What's the easiest way to get
this patch? (Sorry, I'm less familiar with Gerrit...)
On Mon, Mar 23, 2020 at 9:44 AM Simon Marchi <simark at simark.ca> wrote:
> On 2020-03-20 11:12 p.m., Simon Marchi via lttng-dev wrote:
> > So since distutils really wants to compile the Python native modules
> using all the same
> > flags as the Python interpreter was built with, I presume that they
> really assume that
> > you'll be using the exact same toolchain to build your module as was
> used to build the
> > interpreter. Maybe we could just not pass CC/CFLAGS when building the
> Python module,
> > so it will simply be built with the same compiler/linker as Python was
> built with, and
> > we'll avoid all these problems...
> If we want to go this route, here's a patch that implements it.
> This makes it so we don't override the compiler or flags (other than
> necessary includes
> flags) when building the native module. So when configuring with
> CC=clang, the Python
> native module gets built with the Python distribution's default compiler,
> with just the
> flags it wants.
> Could you check if that works with CC=icc as well?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lttng-dev