From: tugouxp <13824125580@163.com>
To: musl@lists.openwall.com
Subject: [musl] how to compile musl pass on X86_64 host?
Date: Wed, 8 Sep 2021 22:14:59 +0800 (CST) [thread overview]
Message-ID: <71329e99.51dc.17bc5c30e55.Coremail.13824125580@163.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2844 bytes --]
Hi guys:
i meet a compile failure when compile the musl libc on PC X86_64,with command "make ARCH=X86_64"
so, how to make this ok?
thanks for your help, the folling is the compile error log.
thank you again!
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
.__st_ctim32.tv_nsec = stx.stx_ctime.tv_nsec,
^~~~~~~~~~~
st_ctim
src/stat/fstatat.c:66:26: warning: excess elements in struct initializer
.__st_ctim32.tv_nsec = stx.stx_ctime.tv_nsec,
^~~
src/stat/fstatat.c:66:26: note: (near initialization for ‘(anonymous)’)
src/stat/fstatat.c: In function ‘fstatat_kstat’:
src/stat/fstatat.c:122:4: error: ‘struct stat’ has no member named ‘__st_atim32’; did you mean ‘st_atim’?
.__st_atim32.tv_sec = kst.st_atime_sec,
^~~~~~~~~~~
st_atim
src/stat/fstatat.c:123:4: error: ‘struct stat’ has no member named ‘__st_atim32’; did you mean ‘st_atim’?
.__st_atim32.tv_nsec = kst.st_atime_nsec,
^~~~~~~~~~~
st_atim
src/stat/fstatat.c:123:26: warning: excess elements in struct initializer
.__st_atim32.tv_nsec = kst.st_atime_nsec,
^~~
src/stat/fstatat.c:123:26: note: (near initialization for ‘(anonymous)’)
src/stat/fstatat.c:124:4: error: ‘struct stat’ has no member named ‘__st_mtim32’; did you mean ‘st_mtim’?
.__st_mtim32.tv_sec = kst.st_mtime_sec,
^~~~~~~~~~~
st_mtim
src/stat/fstatat.c:124:25: warning: excess elements in struct initializer
.__st_mtim32.tv_sec = kst.st_mtime_sec,
^~~
src/stat/fstatat.c:124:25: note: (near initialization for ‘(anonymous)’)
src/stat/fstatat.c:125:4: error: ‘struct stat’ has no member named ‘__st_mtim32’; did you mean ‘st_mtim’?
.__st_mtim32.tv_nsec = kst.st_mtime_nsec,
^~~~~~~~~~~
st_mtim
src/stat/fstatat.c:125:26: warning: excess elements in struct initializer
.__st_mtim32.tv_nsec = kst.st_mtime_nsec,
^~~
src/stat/fstatat.c:125:26: note: (near initialization for ‘(anonymous)’)
src/stat/fstatat.c:126:4: error: ‘struct stat’ has no member named ‘__st_ctim32’; did you mean ‘st_ctim’?
.__st_ctim32.tv_sec = kst.st_ctime_sec,
^~~~~~~~~~~
st_ctim
src/stat/fstatat.c:126:25: warning: excess elements in struct initializer
.__st_ctim32.tv_sec = kst.st_ctime_sec,
^~~
src/stat/fstatat.c:126:25: note: (near initialization for ‘(anonymous)’)
src/stat/fstatat.c:127:4: error: ‘struct stat’ has no member named ‘__st_ctim32’; did you mean ‘st_ctim’?
.__st_ctim32.tv_nsec = kst.st_ctime_nsec,
^~~~~~~~~~~
st_ctim
src/stat/fstatat.c:127:26: warning: excess elements in struct initializer
.__st_ctim32.tv_nsec = kst.st_ctime_nsec,
[-- Attachment #2: Type: text/html, Size: 4326 bytes --]
next reply other threads:[~2021-09-08 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 14:14 tugouxp [this message]
2021-09-08 14:25 ` 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=71329e99.51dc.17bc5c30e55.Coremail.13824125580@163.com \
--to=13824125580@163.com \
--cc=musl@lists.openwall.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).