Simon,
See below...
On Mon, Mar 23, 2020 at 11:24 AM Simon Marchi wrote:
> On 2020-03-23 12:56 p.m., Rocky Dunlap wrote:
> > Simon,
> >
> > Success! This change worked and I was able to build and install with
> icc. Thank you!
>
> Ok, thanks. Out of curiosity, did run a "make check"? That w
On 2020-03-23 12:56 p.m., Rocky Dunlap wrote:
> Simon,
>
> Success! This change worked and I was able to build and install with icc.
> Thank you!
Ok, thanks. Out of curiosity, did run a "make check"? That would validate that
the Python bindings (and everything else) works properly.
> I stil
Simon,
Success! This change worked and I was able to build and install with icc.
Thank you!
I still get a lot of warnings during the build (see below) which seems like
configure should work these out ahead of time. They are easy enough to
ignore, but if support for intel is added, it would be n
On 2020-03-23 12:05 p.m., Rocky Dunlap wrote:
> Simon,
>
> 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...)
>
> Rocky
You need a babeltrace git repository. If you don't already have one, you can
clone it from here
Simon,
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...)
Rocky
On Mon, Mar 23, 2020 at 9:44 AM Simon Marchi wrote:
> On 2020-03-20 11:12 p.m., Simon Marchi via lttng-dev wrote:
> > So since distutils really wants to c
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 yo
