All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Bian, Naimeng" <biannm@cn.fujitsu.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [Question]Remove $BUILDDIR from gcc -v
Date: Fri, 26 Sep 2014 12:06:29 +0100	[thread overview]
Message-ID: <1411729589.4189.110.camel@ted> (raw)
In-Reply-To: <30DC4EDFD798C94083F3E083754532CCCA5E8D@G08CNEXMBPEKD02.g08.fujitsu.local>

On Thu, 2014-09-18 at 09:46 +0000, Bian, Naimeng wrote:
> > > Removing these options is not my purpose, i just want to hide the $BUILDDIR
> > 
> > whats there in BUILDDIR to hide ?
> 
> Thanks for your answer.
> 
> Well, maybe it's a strange case,  but any suggestion it's helpful to me. ^_^
> (I don't think there are some bugs of upstream's poky)
> 
> Of course, we can set BUILDDIR to a safe path such as /workspace,
> but setting BUILDDIR to a secret path caused by a miss operation
> will make a leakage of secret.
> 
> So, is there a method to change BUILDDIR to a relative path not a absolute path.
> Looks like it's not easy. ^_^

I hate to break it to you but there are plenty of other ways the build
path can end up in the resulting binaries, even through things like
debug symbols/information. I'd suggest not putting "secret" information
in the build paths.

Cheers,

Richard



      parent reply	other threads:[~2014-09-26 11:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16  2:44 [Question]Remove $BUILDDIR from gcc -v Bian, Naimeng
2014-09-16  7:21 ` Richard Purdie
2014-09-17  1:04   ` Bian, Naimeng
2014-09-18  7:32     ` Khem Raj
2014-09-18  9:46       ` Bian, Naimeng
2014-09-26  3:29         ` Khem Raj
2014-09-26 11:06         ` Richard Purdie [this message]

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=1411729589.4189.110.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=biannm@cn.fujitsu.com \
    --cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.