From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13477 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: ctype_base.h. Several errors "was not declared in this scope" Date: Sun, 25 Nov 2018 18:19:55 -0500 Message-ID: <20181125231955.GN23599@brightrain.aerifal.cx> References: <20181124214219.GA1006@daniel-HP> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1543187885 8531 195.159.176.226 (25 Nov 2018 23:18:05 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 25 Nov 2018 23:18:05 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-13493-gllmg-musl=m.gmane.org@lists.openwall.com Mon Nov 26 00:18:01 2018 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1gR3f7-00024r-7E for gllmg-musl@m.gmane.org; Mon, 26 Nov 2018 00:18:01 +0100 Original-Received: (qmail 25779 invoked by uid 550); 25 Nov 2018 23:20:09 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 25758 invoked from network); 25 Nov 2018 23:20:08 -0000 Content-Disposition: inline In-Reply-To: <20181124214219.GA1006@daniel-HP> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:13477 Archived-At: On Sat, Nov 24, 2018 at 10:42:19PM +0100, Daniel G. wrote: > Hi all, > I keep on trying to build a cross-compiler toolchain based in musl. I've > left the idea of a multilib one due to conflicting types error (I wrote a > few days ago about alltypes.h conflicting types for 'size_t'). This is likely due to multilib, which needs to be disabled. musl does not do the gcc multilib model of using the same set of headers for pairs of 32- and 64-bit archs that correspond to each other. If you want both you need completely separate toolchains for each. Use --disable-multilib. > Now, also during the second pass of gcc, I've found three make errors. I've > been able to patch two of them (one about the definition of PATH_MAX and > another regarding __GLIBC_PREREQ). This sounds like you're building gcc for a glibc target and not for musl, but it's hard to know for sure with such a vague description. Make sure you've specified x86_64-linux-musl (or whichever arch) on the configure command line. I'm confused why there's a second pass if you're building a cross compiler, though. Multipass only makes sense for a native compiler. > The third one seems to be more complicated, and affects the compilation of > libstdc++-v3. At the end of the mail you can find a bunch of errors on variables not > declared in the scope. This definitely indicates that you're building gcc for a glibc target and not for musl. The files that the errors occurred in are only for use with glibc. Rich