From: "xuchunmei at linux dot alibaba.com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/25994] New: inproper order of PATH set cause wrong unexpected gcc used
Date: Fri, 15 May 2020 06:50:13 +0000 [thread overview]
Message-ID: <bug-25994-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25994
Bug ID: 25994
Summary: inproper order of PATH set cause wrong unexpected gcc
used
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: xuchunmei at linux dot alibaba.com
Target Milestone: ---
Created attachment 12541
--> https://sourceware.org/bugzilla/attachment.cgi?id=12541&action=edit
add default "/usr/bin:/bin" after $PATH
My use case is like this, I install gcc-4.8.5 and devtoolset-9-gcc,
while I set the PATH by "source /opt/rh/devtoolset-9/enable" to use
gcc-9, but when I use "stap test.stap", I always get compile errors
for "gcc: error: unrecognized command line option
‘-fpatchable-function-entry=2’", the option
‘-fpatchable-function-entry=2’ is not supported by gcc-4.8.5 but
supported by gcc-9.
The stap process building always use gcc-4.8.5 from /usr/bin not from
the first path of PATH, such as /opt/rh/devtoolset-9/root/usr/bin/gcc.
As I think the default /usr/bin:/bin should be added after $PATH.
I add an attachment to fix it, please have a review.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-05-15 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 6:50 xuchunmei at linux dot alibaba.com [this message]
2020-05-15 12:40 ` [Bug translator/25994] " fche at redhat dot com
2020-05-16 2:25 ` xuchunmei at linux dot alibaba.com
2020-05-16 3:34 ` xuchunmei at linux dot alibaba.com
2020-05-16 9:51 ` fche at redhat dot com
2020-05-16 10:44 ` xuchunmei at linux dot alibaba.com
2020-07-03 3:01 ` xuchunmei at linux dot alibaba.com
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=bug-25994-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).