Re: alltypes.h error: conflicting types for 'size_t'

[Szabolcs Nagy <nsz@port70.net>]

* Rich Felker <dalias@libc.org> [2018-11-13 20:26:14 -0500]:
> On Wed, Nov 14, 2018 at 01:14:55AM +0100, Szabolcs Nagy wrote:
> > * Daniel G. <audobra@gmail.com> [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).