public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Pavel Tsekov <ptsekov@syntrex.com>
To: Gareth Pearce <tilps@hotmail.com>
Cc: cygwin@cygwin.com
Subject: Re: setlinebuf
Date: Sun, 11 Nov 2001 08:26:00 -0000	[thread overview]
Message-ID: <3BF52D42.88E99373@syntrex.com> (raw)
In-Reply-To: <OE33rIwbyKYdCPubiq4000126f1@hotmail.com>

Gareth Pearce wrote:
> 
> Hi
> 
> umm trying to compile a few things and got setlinebuf not defined a few
> times.  I poked arround the web abit and found that its a BSD extension on
> stdio (provided in glibc as well)- which is used in a few places.  It is
> also incredibly easy to implement as its just a 1 line call to the standard
> setvbuf - obviously its easy to change code that uses it - but having more
> things compile out of the box is seems like a good idea...
> Since its so trivial I would like to add it - however I was unsure as to
> what the appropriate path to getting something added is when it will be in
> the newlib directory.
> 
> Anyone want to point me in the right direction ... prehaps I should be
> heading to a newlib mailinglist ?
> 

Check this link :) 
http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/stdio/setbuffer.c?rev=1.5&content-type=text/x-cvsweb-markup

I think it's appropriate to name the file like this one since the newlib
implementation of stdio is borrowed from BSD. The put it in
newlib/libc/stdio.

And I think you'll have to post the patch to the newlib mailing list
too.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2001-11-16 15:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-11  8:26 setlinebuf Gareth Pearce
2001-11-11  8:26 ` Pavel Tsekov [this message]
2002-05-06 15:17 setlinebuf Chris January
2002-05-06 16:57 ` setlinebuf Christopher Faylor
2002-05-06 21:45   ` setlinebuf Gareth Pearce
2002-05-07  7:43     ` setlinebuf Christopher Faylor
2002-05-07 15:00       ` setlinebuf Gareth Pearce

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=3BF52D42.88E99373@syntrex.com \
    --to=ptsekov@syntrex.com \
    --cc=cygwin@cygwin.com \
    --cc=tilps@hotmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).