mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: tugouxp <13824125580@163.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] how to compile musl pass on X86_64 host?
Date: Wed, 8 Sep 2021 10:25:23 -0400	[thread overview]
Message-ID: <20210908142523.GH13220@brightrain.aerifal.cx> (raw)
In-Reply-To: <71329e99.51dc.17bc5c30e55.Coremail.13824125580@163.com>

On Wed, Sep 08, 2021 at 10:14:59PM +0800, tugouxp wrote:
> 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?

It's recommended to use configure. Running make ARCH=something
directly probably still works (assuming all the things configure would
check come out right) but if you used the literal command above, you
misspelled it. The arch is called x86_64 not X86_64. That might be the
cause of your problem. But really, use configure.

> 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,

These look like it pulled in the wrong arch version some arch-specific
headers, possibly from your misspelling or something else that went
wrong.

      reply	other threads:[~2021-09-08 14:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08 14:14 tugouxp
2021-09-08 14:25 ` 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:
  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=20210908142523.GH13220@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=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).