From: maximilian attems <max@stro.at>
To: Jilles Tjoelker <jilles@stack.nl>
Cc: Herbert Xu <herbert@gondor.hengli.com.au>,
klibc@zytor.com, dash@vger.kernel.org
Subject: Re: [PATCH] JOBS: fix klibc DEBUG compilation
Date: Sat, 4 Jun 2011 06:45:59 +0000 [thread overview]
Message-ID: <20110604064559.GD22026@vostochny.stro.at> (raw)
In-Reply-To: <20110603181302.GA13418@stack.nl>
On Fri, Jun 03, 2011 at 08:13:02PM +0200, Jilles Tjoelker wrote:
> > src/show.c | 2 ++
> > 1 files changed, 2 insertions(+), 0 deletions(-)
>
> > diff --git a/src/show.c b/src/show.c
> > index 14dbef3..b4160e1 100644
> > --- a/src/show.c
> > +++ b/src/show.c
> > @@ -394,7 +394,9 @@ opentrace(void)
> > if ((flags = fcntl(fileno(tracefile), F_GETFL, 0)) >= 0)
> > fcntl(fileno(tracefile), F_SETFL, flags | O_APPEND);
> > #endif
> > +#ifndef SMALL
> > setlinebuf(tracefile);
> > +#endif /* SMALL */
> > fputs("\nTracing started.\n", tracefile);
> > }
> > #endif /* DEBUG */
>
> Why not just replace the non-standard setlinebuf() call with the
> standard setvbuf(tracefile, NULL, _IOLBF, 0); ? This appears to work
> just as well on FreeBSD and is C99 compliant (no POSIX needed here).
>
> The #define SMALL is only for disabling line editing and history (using
> libedit). Setting the trace file line buffered is useful regardless of
> that.
If one doesn't support libedit one is assumed to define SMALL
and klibc does such.
http://www.spinics.net/lists/dash/msg00311.html
oh and I seem to not have recieved Herbert's answer from last Sept.
http://www.spinics.net/lists/dash/msg00367.html
I'll respin the patch based on it, thank you.
--
maks
prev parent reply other threads:[~2011-06-04 6:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 17:38 [PATCH] JOBS: fix klibc DEBUG compilation maximilian attems
2011-06-03 18:13 ` Jilles Tjoelker
2011-06-04 6:45 ` maximilian attems [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=20110604064559.GD22026@vostochny.stro.at \
--to=max@stro.at \
--cc=dash@vger.kernel.org \
--cc=herbert@gondor.hengli.com.au \
--cc=jilles@stack.nl \
--cc=klibc@zytor.com \
/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