[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<OSYP286MB01817DC4CB93CA1A620C95FCFE1A0@OSYP286MB0181.JPNP286.PROD.OUTLOOK.COM>
Date: Fri, 23 Oct 2020 15:19:05 +0800
From: "Chen Wang" <unicorn_wang@...look.com>
To: unicorn_wang <unicorn_wang@...look.com>,
musl <musl@...ts.openwall.com>
Subject: 回复: issue when running libc-test
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.
Best Regards
Wang Chen
发件人： Chen Wang
发送时间： 2020-10-23 15:08
收件人： musl
抄送： unicorn_wang
主题： issue when running libc-test
Hi, I'm not sure it's ok to post issue report about libc-test to this maillist, if it is not ok, please let me know.
I downloaded the latest libc-test and run make, commit id of latest master is 287fe555a8279fab14e89e7cd64787d234a30ebf
$ git clone git://repo.or.cz/libc-test
$ cd libc-test
$ CC=../install/bin/musl-gcc make
I checked the output and see following error report:
../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)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
I double checked and found it is due to lacking of "src/common/options.h", I found this file is not created successfully, and there is only src/common/options.h.in, that's make the build failed.
Best Regards
Wang Chen
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.
