From: Rocky Dunlap via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: Babeltrace2 - compilation error with intel18
Date: Fri, 20 Mar 2020 15:10:26 -0600 [thread overview]
Message-ID: <CADtyBo7jFiv-E-DCp4kYfY7WRSLsN3Oos6iRr35Sy9o=iNZKOg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1037 bytes --]
I am trying to compile BT2 with Python bindings using Intel18. I receive
the following error during the build:
In file included from py-common.c(31):
/apps/intel/intelpython3/include/python3.6m/Python.h(149): error #193: zero
used for undefined preprocessing identifier "_MSC_VER"
#if _MSC_VER
^
In file included from py-common.c(31):
/apps/intel/intelpython3/include/python3.6m/Python.h(151): error #193: zero
used for undefined preprocessing identifier "__clang__"
#elif __clang__ || __GNUC__
^
py-common.c(187): error #3179: deprecated conversion of string literal to
char* (should be const char*)
format_exc_func_name = py_exc_tb ? "format_exception" :
^
compilation aborted for py-common.c (code 2)
make[2]: *** [py-common.lo] Error 1
make[2]: Leaving directory
`/home/Rocky.Dunlap/babeltrace/babeltrace2-2.0.2/src/py-common'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/home/Rocky.Dunlap/babeltrace/babeltrace2-2.0.2/src'
Rocky
[-- Attachment #1.2: Type: text/html, Size: 1259 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2020-03-20 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 21:10 Rocky Dunlap via lttng-dev [this message]
2020-03-20 21:47 ` Babeltrace2 - compilation error with intel18 Simon Marchi via lttng-dev
2020-03-20 21:55 ` Rocky Dunlap via lttng-dev
2020-03-20 22:20 ` Simon Marchi via lttng-dev
2020-03-20 22:32 ` Rocky Dunlap via lttng-dev
2020-03-21 3:12 ` Simon Marchi via lttng-dev
2020-03-23 15:44 ` Simon Marchi via lttng-dev
2020-03-23 16:05 ` Rocky Dunlap via lttng-dev
2020-03-23 16:14 ` Simon Marchi via lttng-dev
2020-03-23 16:56 ` Rocky Dunlap via lttng-dev
2020-03-23 17:24 ` Simon Marchi via lttng-dev
2020-03-23 17:37 ` Rocky Dunlap via lttng-dev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADtyBo7jFiv-E-DCp4kYfY7WRSLsN3Oos6iRr35Sy9o=iNZKOg@mail.gmail.com' \
--to=lttng-dev@lists.lttng.org \
--cc=dunlap@ucar.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).