From: Jonathan Rajotte-Julien via lttng-dev <lttng-dev@lists.lttng.org>
To: "Weber, John" <jweber1@ball.com>
Cc: "'lttng-dev@lists.lttng.org'" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] lttng 2.12 install
Date: Fri, 20 Nov 2020 13:47:46 -0500 [thread overview]
Message-ID: <20201120184746.GF8709@joraj-alpa> (raw)
In-Reply-To: <326539938460471c975e791ce6b1c775@ball.com>
Hi John,
This does not seems to be directly related to the lttng-modules project.
This errors seems to arise because of the compiler you are using to compile
lttng-modules (kernel modules). The RETPOLINE check is part of the kernel build
system, not directly lttng-modules.
I would recommend that you take a look at the /proc/version file and the
compiler that was used to compile your kernel.
Also note that EfficiOS [1] provide commercial support if you ever need more
in-depth support.
Cheers
[1] https://www.efficios.com/contact/
On Fri, Nov 20, 2020 at 05:43:00PM +0000, Weber, John via lttng-dev wrote:
> Hi, I have a centos 7.8 workstation that I'm trying to install lttng-modules & lttng-tools from source. Based on your install instructions I'm working on installing the modules part first and its failing. I am getting the error:
> Make entering directory /usr/src/kernels/3.10.0-1127.19.1.el7.x86_64
> Arch/x86/Makefile:166 *** CONFIG_RETPOLINE=y, but not supported by the compiler. Compiler update recommended... stop
> Make: modules error 2
>
> Help, how can I get this program to install? Im stuck. Also, my work environment is classified so there is no access to internet from high side.
>
> ----------------------------
> John Weber
> Ball Aerospace
> ITS ND System Administrator
> 10 Longs Peak Dr., Broomfield, CO 80021
> C: 303-807-3608 P: 303-234-2103
> E: jweber1@ball.com
>
>
> [cid:image001.jpg@01D6BF29.AD6C5250]
>
>
> [cid:image002.jpg@01D6BF29.AD6C5250]<http://www.ball.com/aerospace>
>
> This message and any enclosures are intended only for the addressee. Please
> notify the sender by email if you are not the intended recipient. If you are
> not the intended recipient, you may not use, copy, disclose, or distribute this
> message or its contents or enclosures to any other person and any such actions
> may be unlawful. Ball reserves the right to monitor and review all messages
> and enclosures sent to or from this email address.
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Jonathan Rajotte-Julien
EfficiOS
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2020-11-20 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 17:43 [lttng-dev] lttng 2.12 install Weber, John via lttng-dev
2020-11-20 18:47 ` Jonathan Rajotte-Julien via lttng-dev [this message]
2020-11-24 19:22 ` [lttng-dev] [EXTERNAL] " Weber, John via lttng-dev
2020-11-24 20:21 ` Jonathan Rajotte-Julien via lttng-dev
2020-11-24 21:02 ` Weber, John via lttng-dev
2020-11-24 21:18 ` Jonathan Rajotte-Julien via lttng-dev
2020-11-24 21:41 ` Michael Jeanson via lttng-dev
2020-11-24 22:01 ` Weber, John 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=20201120184746.GF8709@joraj-alpa \
--to=lttng-dev@lists.lttng.org \
--cc=jonathan.rajotte-julien@efficios.com \
--cc=jweber1@ball.com \
/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).