public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernard.van.duijnen at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/53529] assembler errors while building a cross compiler if . (dot) is in your PATH
Date: Wed, 30 May 2012 15:55:00 -0000	[thread overview]
Message-ID: <bug-53529-4-rqtxNQiTQm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53529-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53529

--- Comment #2 from Bernard van Duijnen <bernard.van.duijnen at oracle dot com> 2012-05-30 15:49:43 UTC ---
(In reply to comment #1)
> Don't do it then?  Having . in $PATH is a severe security issue anyway.

Typically it is unsecure yes, but not always. For instance on my ubuntu
laptop where I am the one and only user I do not think that is an issue.

Its easy to fix your PATH to solve it, but only once you know that is
the issue, just a check to catch the situation and give a warning is a
sufficient solution.


  parent reply	other threads:[~2012-05-30 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 15:29 [Bug c/53529] New: " bernard.van.duijnen at oracle dot com
2012-05-30 15:45 ` [Bug c/53529] " jakub at gcc dot gnu.org
2012-05-30 15:55 ` bernard.van.duijnen at oracle dot com [this message]
2013-02-09 20:31 ` karlson2k at gmail dot com
2013-02-09 23:01 ` pinskia at gcc dot gnu.org

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-53529-4-rqtxNQiTQm@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).