Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Michael Jeanson via lttng-dev <lttng-dev@lists.lttng.org>
To: "Weber, John" <jweber1@ball.com>,
	'Jonathan Rajotte-Julien' <jonathan.rajotte-julien@efficios.com>
Cc: "'lttng-dev@lists.lttng.org'" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] [EXTERNAL] Re: lttng 2.12 install
Date: Tue, 24 Nov 2020 16:41:04 -0500	[thread overview]
Message-ID: <aad4e816-2ff5-5f8b-fe56-108b17fcaf47@efficios.com> (raw)
In-Reply-To: <aefcb4673adb4b3980bb0612a81f8d87@ball.com>

On 2020-11-24 16 h 02, Weber, John via lttng-dev wrote:
> Ok, it I get what you're saying then I am modifying make on the command line while running make? Still the same problem. I don't think it is using the gcc I am specifying as it continues to look in: /usr/src/kernels/3.10.0-1127.19.1.el7.x86_64/
> And I suspect it is still seeing the OS version of gcc (4.8.5) instead of the 6.3.1 provided by devtoolset-6.
> Do you have some pixy dust??

Running this will get you verbose output while building which should 
help you determine which compiler and other tools are used :

   make CC="/opt/rh/devtoolset-6/root/bin/gcc" V=1

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  parent reply	other threads:[~2020-11-24 21:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 17:43 [lttng-dev] " Weber, John via lttng-dev
2020-11-20 18:47 ` Jonathan Rajotte-Julien via lttng-dev
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 [this message]
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=aad4e816-2ff5-5f8b-fe56-108b17fcaf47@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=jonathan.rajotte-julien@efficios.com \
    --cc=jweber1@ball.com \
    --cc=mjeanson@efficios.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