From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13444 Path: news.gmane.org!.POSTED!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: alltypes.h error: conflicting types for 'size_t' Date: Wed, 14 Nov 2018 14:57:52 +0100 Message-ID: <20181114135752.GG21289@port70.net> References: <20181113205600.GA16442@daniel-HP> <20181114001455.GF21289@port70.net> <20181114012614.GI5150@brightrain.aerifal.cx> 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 1542203761 8902 195.159.176.226 (14 Nov 2018 13:56:01 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 14 Nov 2018 13:56:01 +0000 (UTC) User-Agent: Mutt/1.10.1 (2018-07-13) Cc: "Daniel G." To: musl@lists.openwall.com Original-X-From: musl-return-13460-gllmg-musl=m.gmane.org@lists.openwall.com Wed Nov 14 14:55:57 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 1gMve8-0002Bh-Pv for gllmg-musl@m.gmane.org; Wed, 14 Nov 2018 14:55:56 +0100 Original-Received: (qmail 13371 invoked by uid 550); 14 Nov 2018 13:58:05 -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 13353 invoked from network); 14 Nov 2018 13:58:05 -0000 Mail-Followup-To: musl@lists.openwall.com, "Daniel G." Content-Disposition: inline In-Reply-To: <20181114012614.GI5150@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:13444 Archived-At: * Rich Felker [2018-11-13 20:26:14 -0500]: > On Wed, Nov 14, 2018 at 01:14:55AM +0100, Szabolcs Nagy wrote: > > * Daniel G. [2018-11-13 21:56:00 +0100]: > > > /mnt/clfs_MUSL/sources/gcc-8.2.0/build/./gcc/xgcc > > > -B/mnt/clfs_MUSL/sources/gcc-8.2.0/build/./gcc/ > > > -B/cross-tools/x86_64-unknown-linux-gnu/bin/ > > > -B/cross-tools/x86_64-unknown-linux-gnu/lib/ -isystem > > > /cross-tools/x86_64-unknown-linux-gnu/include -isystem > > > /cross-tools/x86_64-unknown-linux-gnu/sys-include -g -O2 -O2 -g -O2 > > > -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing > > > -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes > > > -Wold-style-definition -isystem ./include -fpic -mlong-double-80 > > > -DUSE_ELF_SYMVER -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector > > > -fpic -mlong-double-80 -DUSE_ELF_SYMVER -I. -I. -I../.././gcc > > > -I../../../libgcc -I../../../libgcc/. -I../../../libgcc/../gcc > > > -I../../../libgcc/../include -I../../../libgcc/config/libbid > > > -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS -DUSE_TLS -o generic-morestack.o > > > -MT generic-morestack.o -MD -MP -MF generic-morestack.dep -c > > > ../../../libgcc/generic-morestack.c -fvisibility=hidden -DHIDE_EXPORTS > > > > > .... > > > In file included from > > > /mnt/clfs_MUSL/sources/gcc-8.2.0/build/gcc/include-fixed/stdio.h:36, > > > from ../../../libgcc/../gcc/tsystem.h:87, > > > from ../../../libgcc/generic-morestack.c:30: > > > /mnt/clfs_MUSL/tools/include/bits/alltypes.h:136:24: error: conflicting > > > types for 'size_t' > > > typedef unsigned _Addr size_t; > > > ^~~~~~ > > > In file included from ../../../libgcc/../gcc/tsystem.h:44, > > > from ../../../libgcc/generic-morestack.c:30: > > > /mnt/clfs_MUSL/sources/gcc-8.2.0/build/gcc/include/stddef.h:216:23: note: > > > previous declaration of 'size_t' was here > > > typedef __SIZE_TYPE__ size_t; > > > ^~~~~~ > > > > it is not ideal that both musl and gcc headers get > > included with the typedefs, but i don't see why > > they are in conflict: > > > > both typedefs should expand to 'unsigned long' > > (if not then something is very wrong) > > > > you can try to rerun that build command with -E > > instead of -c to see the actual size_t definitions > > after macro expansion. > > > > (i assume multilib breaks it somehow, but i don't > > see how) > > It's a bug in the gcc build process if the gcc-provided headers get > used at all with musl. This might be multilib-dependent. I've not i think the same happens in mcm when libgcc is built, because of the -B.../gcc -I.../gcc cflags, gcc/include and gcc/ are in the search path before the libc headers, but the typedefs happen to not collide. > tested with multilib since it definitely does not work with musl > anyway (gcc's multilib assumes the same include dir works for both of > the 'corresponding' 32- and 64-bit archs, which is not the case for > musl).