mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Cc: "Daniel G." <audobra@gmail.com>
Subject: Re: alltypes.h error: conflicting types for 'size_t'
Date: Wed, 14 Nov 2018 01:14:55 +0100	[thread overview]
Message-ID: <20181114001455.GF21289@port70.net> (raw)
In-Reply-To: <20181113205600.GA16442@daniel-HP>

* 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)

> ../../../libgcc/shared-object.mk:14: recipe for target
> 'generic-morestack.o' failed
> make[1]: *** [generic-morestack.o] Error 1


  reply	other threads:[~2018-11-14  0:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 20:56 Daniel G.
2018-11-14  0:14 ` Szabolcs Nagy [this message]
2018-11-14  1:26   ` Rich Felker
2018-11-14 13:57     ` Szabolcs Nagy

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=20181114001455.GF21289@port70.net \
    --to=nsz@port70.net \
    --cc=audobra@gmail.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).