mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Re: [PATCH] Include missing reference to stdio.h for EOF definition
Date: Thu, 25 Feb 2016 13:27:54 -0500	[thread overview]
Message-ID: <20160225182754.GV9349@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAM5B0qJc_8_a+c84cqsDkhzeCvuF3xczCSYBp7FKnj96p1b7jQ@mail.gmail.com>

On Thu, Feb 25, 2016 at 10:50:01AM +0100, Michael Meeuwisse wrote:
> Following up. I know this is a rather silly patch to accept, but I'm trying
> to get OSv (http://osv.io) up to date. It currently uses 0.9.12 which did
> have this line, but it was dropped (imho erroneously) last June in
> following commit;
> http://git.musl-libc.org/cgit/musl/commit/?id=1507ebf837334e9e07cfab1ca1c2e88449069a80
> 
> Since OSv does a few.. unconventional.. things in regards to musl
> inclusion, relying on stdio.h being included implicitly here doesn't work,
> and working around this omission is a far larger effort than simply
> correcting it upstream. Not saying I'm not trying to make the inclusion
> more conventional, just that there's bigger fish to fry at the moment.

Thanks for the explanation of your motivation. I wasn't opposed to
this patch but was curious why it mattered. I'd actually like to go
through the source at some point and find places we're making
unreasonable assumptions about implicit inclusion, and also get rid of
some of the unnecessary implicit inclusions (e.g. stdio.h from libc.h
makes no sense and is probably just there because __lockfile is
declared in a poorly chosen place). But for now I'm happy to accept
this patch as a start.

Rich



> On Tue, Feb 23, 2016 at 11:49 PM, Michael Meeuwisse <mickeymeeuw@gmail.com>
> wrote:
> 
> > No binary changes as it was already included implicitly;
> > . src/multibyte/internal.h
> > .. ./src/internal/locale_impl.h
> > ... ./src/internal/libc.h
> > .... ./include/stdio.h
> >
> > However, all evidence suggest this to be a fortunate accident rather than
> > an intentional design choice.
> >
> > Signed-off-by: Michael Meeuwisse <mickeymeeuw+git@gmail.com>
> > ---
> >  src/multibyte/wctob.c | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/src/multibyte/wctob.c b/src/multibyte/wctob.c
> > index 4aeda6a..b484a3f 100644
> > --- a/src/multibyte/wctob.c
> > +++ b/src/multibyte/wctob.c
> > @@ -1,4 +1,5 @@
> >  #include <wchar.h>
> > +#include <stdio.h>
> >  #include <stdlib.h>
> >  #include "internal.h"
> >
> > --
> > 2.5.0
> >
> >


      reply	other threads:[~2016-02-25 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 22:49 Michael Meeuwisse
2016-02-25  9:50 ` Michael Meeuwisse
2016-02-25 18:27   ` Rich Felker [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=20160225182754.GV9349@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).