[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM5B0qJc_8_a+c84cqsDkhzeCvuF3xczCSYBp7FKnj96p1b7jQ@mail.gmail.com>
Date: Thu, 25 Feb 2016 10:50:01 +0100
From: Michael Meeuwisse <mickeymeeuw@...il.com>
To: musl@...ts.openwall.com
Cc: Michael Meeuwisse <mickeymeeuw+git@...il.com>
Subject: Re: [PATCH] Include missing reference to stdio.h for EOF definition
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.
Thank you,
Michael
On Tue, Feb 23, 2016 at 11:49 PM, Michael Meeuwisse <mickeymeeuw@...il.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@...il.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
>
>
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
