mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <>
To: 程智星 <>
Subject: Re: [musl] Re: Re: On the redefinition of stdin, stdout, etc. in stdio. h
Date: Sun, 2 Jul 2023 22:30:08 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Jul 03, 2023 at 08:37:17AM +0800, 程智星 wrote:
> hi,friend:
> I have a question to ask:
> 1. The stdin and stdout are redefined in the stdio. h file in the Musl source code, as follows:
> extern FILE *const stdin;
> extern FILE *const stdout;
> extern FILE *const stderr;
> #define stdin  (stdin)
> #define stdout (stdout)
> #define stderr (stderr)
> but,In glibc, they are only redefined as themselves, as follows:
> /* Standard streams.  */
> extern FILE *stdin;             /* Standard input stream.  */
> extern FILE *stdout;            /* Standard output stream.  */
> extern FILE *stderr;            /* Standard error output stream.  */
> /* C89/C99 say they're macros.  Make them happy.  */
> #define stdin stdin
> #define stdout stdout
> #define stderr stderr
> Based on what considerations we will make this change? 
> 2. Based on the above modifications, I will report the following errors when compiling packages such as lcr and lxc using Musl as the basic library for yocto embedded compilation:
>  -o json/.libs/liblxc_la-json_common.o
> | In file included from ../../../lxc-4.0.3/src/lxc/json/read-file.h:5,
> |                  from ../../../lxc-4.0.3/src/lxc/json/defs.c:6:
> | ../../../lxc-4.0.3/src/lxc/json/defs.c: In function 'make_defs_hook':
> | ../../../lxc-4.0.3/src/lxc/json/defs.c:86:26: error: expected identifier before '(' token
> |    86 |                 if (ctx-&gt;stderr &gt; 0)
> |       |                          ^~~~~~
> | ../../../lxc-4.0.3/src/lxc/json/defs.c:87:34: error: expected identifier before '(' token
> |    87 |                     fprintf(ctx-&gt;stderr, "WARNING: unknown key found: %s\n", tree-&gt;u.object.keys[i]);
> |       |                                  ^~~~~~
> | ../../../lxc-4.0.3/src/lxc/json/defs.c:87:21: error: too few arguments to function 'fprintf'
> |    87 |                     fprintf(ctx-&gt;stderr, "WARNING: unknown key found: %s\n", tree-&gt;u.object.keys[i]);
> |       |                     ^~~~~~~
> | In file included from ../../../lxc-4.0.3/src/lxc/json/read-file.h:5,
> |                  from ../../../lxc-4.0.3/src/lxc/json/defs.c:6:
> Is there a solution to this error report; I tried to synchronize
> their definitions in the Musl source code with those in Glibc, and
> there was no problem compiling images. Can it be modified to be
> consistent with glibc?

No, this is a bug in the application. Per 7.21.1 ¶3, stdin, stdout,
and stderr are macros which expand to expressions. And per 7.1.3
"Reserved Identifiers", ¶2, "If the program declares or defines an
identifier in a context in which it is reserved (other than as allowed
by 7.1.4), or defines a reserved identifier as a macro name, the
behavior is undefined."

An application cannot use the names stdin, stdout, or stderr in the
manner above if it is including stdio.h. The names of those struct
members need to be changed to something that is not in the reserved

If anything, at some point we may be making changes further in the
opposite direction, so that the expressions are not lvalues. This has
value to catch/preclude other types of application errors. musl would
not give up the ability to do things like this for the sake of
compatibility with erroneous application sources that could easily be


      reply	other threads:[~2023-07-03  2:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2023-07-03  0:37   ` 程智星
2023-07-03  2:30     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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

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).