From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 8646 invoked from network); 8 Sep 2021 14:25:39 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 8 Sep 2021 14:25:39 -0000 Received: (qmail 18033 invoked by uid 550); 8 Sep 2021 14:25:37 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 18013 invoked from network); 8 Sep 2021 14:25:36 -0000 Date: Wed, 8 Sep 2021 10:25:23 -0400 From: Rich Felker To: tugouxp <13824125580@163.com> Cc: musl@lists.openwall.com Message-ID: <20210908142523.GH13220@brightrain.aerifal.cx> References: <71329e99.51dc.17bc5c30e55.Coremail.13824125580@163.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <71329e99.51dc.17bc5c30e55.Coremail.13824125580@163.com> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] how to compile musl pass on X86_64 host? 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.