Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
 <OSYP286MB01815D33AD5B3901346ED12DFE1A0@OSYP286MB0181.JPNP286.PROD.OUTLOOK.COM>
Date: Fri, 23 Oct 2020 17:16:18 +0800
From: "Chen Wang" <unicorn_wang@...look.com>
To: musl <musl@...ts.openwall.com>
Cc: musl <musl@...ts.openwall.com>
Subject: Re: Re:回复: issue when running libc-test

I see tons of error indications in build output, such as below:

```
src/common/runtest.exe -w '' src/functional/ungetc-static.exe >src/functional/ungetc-static.err || true
/bin/sh: 1: src/common/runtest.exe: not found
```

I'm afraid this tell us some testcases will not be run fully.



Best Regards

汪辰(Wang Chen)
 
发件人: Szabolcs Nagy
发送时间: 2020-10-23 17:11
收件人: Chen Wang
抄送: musl
主题: Re: Re:[musl]回复: issue when running libc-test
* Chen Wang <unicorn_wang@...look.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@...look.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.

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.