public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	Nir Tzachar <nir.tzachar@gmail.com>
Subject: Re: [PATCH 1/4] kbuild: don't assign `stdout' and `stderr'
Date: Thu, 28 Oct 2010 00:56:52 +0200	[thread overview]
Message-ID: <4CC8AE34.30607@suse.cz> (raw)
In-Reply-To: <AANLkTimaeNoK9yDyoFHma_zLu+euSjXfni298_nEKHWK@mail.gmail.com>

On 21.10.2010 04:22, Arnaud Lacombe wrote:
> Hi Michal,
> 
> On Tue, Aug 17, 2010 at 4:27 AM, Michal Marek <mmarek@suse.cz> wrote:
>> On Mon, Aug 16, 2010 at 12:19:03AM -0400, Arnaud Lacombe wrote:
>>> These may not be modifiable, as per C99 comment:
>>>
>>> section 7.19.5.4, note 232:
>>> "
>>> The primary use of the freopen function is to change the file associated with a
>>> standard text stream (stderr, stdin, or stdout), as those identifiers need not
>>> be modifiable lvalues to which the value returned by the fopen function may be
>>> assigned.
>>> "
>>>
>>> Use a duplicate of stdout as ncurses' output terminal, then redirect it
>>> to /dev/null for conf_write().
>>
>> I would much rather get rid of this redirection completely. The config
>> library should not play with stdout, but let the frontends display
>> messages as they wish. This patch does it for nconfig. Nir, what do you
>> think?
>>
> any news about this ? AFAICS, it not in `kbuild/kconfig'.

Sorry, I forgot about this patch. It's merged into the kconfig branch now.

Michal

      reply	other threads:[~2010-10-27 22:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-16  4:19 [PATCH 1/4] kbuild: don't assign `stdout' and `stderr' Arnaud Lacombe
2010-08-16  4:19 ` [PATCH 2/4] kbuild: don't include `check-lxdialog' ldflags in global HOST_LOADLIBES Arnaud Lacombe
2010-08-17  9:01   ` Michal Marek
2010-08-16  4:19 ` [PATCH 3/4] kbuild: `nconf' needs -lintl Arnaud Lacombe
2010-08-17  9:00   ` Michal Marek
2010-08-17 15:55     ` Arnaud Lacombe
2010-08-23  0:03       ` [PATCH] kbuild: don't overwrite HOST_EXTRACFLAGS Arnaud Lacombe
2010-08-23  0:17         ` Arnaud Lacombe
2010-08-26 12:00           ` Michal Marek
2010-08-26 12:11             ` Sam Ravnborg
2010-08-16  4:19 ` [PATCH 4/4] kbuild: fix typo Arnaud Lacombe
2010-08-17  8:27 ` [PATCH 1/4] kbuild: don't assign `stdout' and `stderr' Michal Marek
2010-08-17 15:28   ` Arnaud Lacombe
2010-08-18  5:16   ` Nir Tzachar
2010-10-21  2:22   ` Arnaud Lacombe
2010-10-27 22:56     ` Michal Marek [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=4CC8AE34.30607@suse.cz \
    --to=mmarek@suse.cz \
    --cc=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=nir.tzachar@gmail.com \
    --cc=sam@ravnborg.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