Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Hide troublesome environment variables from sub processes [Re: svn commit: trunk/buildroot]
Date: Wed, 20 Jun 2007 11:10:50 +0200	[thread overview]
Message-ID: <20070620091049.GB21092@aon.at> (raw)
In-Reply-To: <20070619151928.B270A485C2@busybox.net>

On Tue, Jun 19, 2007 at 08:19:28AM -0700, jacmet at uclibc.org wrote:
>Author: jacmet
>Date: 2007-06-19 08:19:27 -0700 (Tue, 19 Jun 2007)
>New Revision: 18856
>
>Log:
>Hide troublesome environment variables from sub processes
>(E.G. screws up gdb, busybox, ..)
>
>
>Modified:
>   trunk/buildroot/Makefile

You should check for these in dependencies.sh instead.

  reply	other threads:[~2007-06-20  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 15:19 [Buildroot] svn commit: trunk/buildroot jacmet at uclibc.org
2007-06-20  9:10 ` Bernhard Fischer [this message]
2007-06-20  9:59   ` [Buildroot] Hide troublesome environment variables from sub processes [Re: svn commit: trunk/buildroot] Peter Korsgaard

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=20070620091049.GB21092@aon.at \
    --to=rep.dot.nop@gmail.com \
    --cc=buildroot@busybox.net \
    /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