mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: Chen Wang <unicorn_wang@outlook.com>
Cc: musl <musl@lists.openwall.com>
Subject: Re: Re: [musl]回复: issue when running libc-test
Date: Fri, 23 Oct 2020 11:11:39 +0200	[thread overview]
Message-ID: <20201023091139.GW2947641@port70.net> (raw)
In-Reply-To: <OSYP286MB0181776B5F19465E1233C99DFE1A0@OSYP286MB0181.JPNP286.PROD.OUTLOOK.COM>

* Chen Wang <unicorn_wang@outlook.com> [2020-10-23 16:53:14 +0800]:
> Yes, I think it should be conditional silenced for musl, otherwise it has blocked following builds, such as for main.exe and runtest.exe. 
> So I think it is an issue, right? 

oh
for me it does ot break the entire test build, just src/api/main.exe.

> 发件人: Szabolcs Nagy
> 发送时间: 2020-10-23 16:48
> 收件人: Chen Wang
> 抄送: musl
> 主题: Re: [musl]回复: issue when running libc-test
> * Chen Wang <unicorn_wang@outlook.com> [2020-10-23 15:19:05 +0800]:
> > Correct some comments in last email. The issue is not due to lacking of header file, it should be due to some constants are lost, I paste the whole error report here FYR:
> > 
> > ../install/bin/musl-gcc -Isrc/common -Isrc/common -pipe -std=c99 -D_POSIX_C_SOURCE=200809L -Wall -Wno-unused-function -Wno-missing-braces -Wno-unused -Wno-overflow -Wno-unknown-pragmas -fno-builtin -frounding-math -Werror=implicit-function-declaration -Werror=implicit-int -Werror=pointer-sign -Werror=pointer-arith -g -D_FILE_OFFSET_BITS=64 -pedantic-errors -Werror -Wno-unused -D_XOPEN_SOURCE=700  -c -o src/api/unistd.o src/api/unistd.c 2>src/api/unistd.o.err || echo BUILDERROR src/api/unistd.o; cat src/api/unistd.o.err
> > BUILDERROR src/api/unistd.o
> > src/api/unistd.c: In function ‘f’:
> > src/api/unistd.c:87:3: error: ‘_CS_POSIX_V7_THREADS_CFLAGS’ undeclared (first use in this function)
> >    87 | C(_CS_POSIX_V7_THREADS_CFLAGS)
> >       |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> > src/api/unistd.c:5:21: note: in definition of macro ‘C’
> >     5 | #define C(n) switch(n){case n:;}
> >       |                     ^
> > src/api/unistd.c:87:3: note: each undeclared identifier is reported only once for each function it appears in
> >    87 | C(_CS_POSIX_V7_THREADS_CFLAGS)
> >       |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> > src/api/unistd.c:5:21: note: in definition of macro ‘C’
> >     5 | #define C(n) switch(n){case n:;}
> >       |                     ^
> > src/api/unistd.c:88:3: error: ‘_CS_POSIX_V7_THREADS_LDFLAGS’ undeclared (first use in this function)
> >    88 | C(_CS_POSIX_V7_THREADS_LDFLAGS)
> >       |   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > src/api/unistd.c:5:21: note: in definition of macro ‘C’
> >     5 | #define C(n) switch(n){case n:;}
> >       |                     ^
> > src/api/unistd.c:117:3: error: ‘_PC_TIMESTAMP_RESOLUTION’ undeclared (first use in this function)
> >   117 | C(_PC_TIMESTAMP_RESOLUTION)
> >       |   ^~~~~~~~~~~~~~~~~~~~~~~~
> > src/api/unistd.c:5:21: note: in definition of macro ‘C’
> >     5 | #define C(n) switch(n){case n:;}
> >       |                     ^
> > src/api/unistd.c:238:3: error: ‘_SC_XOPEN_UUCP’ undeclared (first use in this function)
> >   238 | C(_SC_XOPEN_UUCP)
> >       |   ^~~~~~~~~~~~~~
> > src/api/unistd.c:5:21: note: in definition of macro ‘C’
> >     5 | #define C(n) switch(n){case n:;}
> >       |                     ^
> > 
> > and this would cause the following main.exe and runtest.exe failed to be built.
>  
> this is expected:
>  
> posix requires these macros but musl does not define them.
> in practice they are unlikely to be needed so i guess
> these should be silenced in some way.

  reply	other threads:[~2020-10-23  9:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23  7:08 [musl] " Chen Wang
2020-10-23  7:19 ` [musl] 回复: " Chen Wang
2020-10-23  8:48   ` Szabolcs Nagy
2020-10-23  8:53     ` Re: [musl]回复: " Chen Wang
2020-10-23  9:11       ` Szabolcs Nagy [this message]
2020-10-23  9:16         ` [musl] Re: " Chen Wang
2020-10-23 16:28           ` Szabolcs Nagy
2020-10-24 15:47       ` Re: [musl]回复: " Rich Felker

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=20201023091139.GW2947641@port70.net \
    --to=nsz@port70.net \
    --cc=musl@lists.openwall.com \
    --cc=unicorn_wang@outlook.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).