From: Mark Greer <mgreer@animalcreek.com>
To: Oliver <oohall@gmail.com>
Cc: Mark Greer <mgreer@animalcreek.com>,
Christophe LEROY <christophe.leroy@c-s.fr>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] powerpc/boot: Remove duplicate typedefs from libfdt_env.h
Date: Fri, 30 Mar 2018 19:42:29 -0700 [thread overview]
Message-ID: <20180331024229.GA18304@animalcreek.com> (raw)
In-Reply-To: <20180330022652.GB20304@animalcreek.com>
On Thu, Mar 29, 2018 at 07:26:52PM -0700, Mark Greer wrote:
> On Thu, Mar 29, 2018 at 07:22:50PM -0700, Mark Greer wrote:
> > On Tue, Mar 20, 2018 at 10:55:07AM +1100, Oliver wrote:
>
> > > Yeah that's pretty odd. It might be a bug in your specific version of
> > > GCC since I can't replicate it with this dumb test case:
> > >
> > > #include <stdio.h>
> > > typedef unsigned int u32;
> > >
> > > typedef u32 uint32_t;
> > > typedef u32 uint32_t;
> > >
> > > int main(void) {
> > > uint32_t test = 0;
> > > printf("%u\n", test);
> > > return 0;
> > > }
> > >
> > > Does that result in an error?
> >
> > Hi Oliver. I'm very sorry for the long delay in responding.
> >
> > This fail to compile too:
> >
> > $ cat test.c
> > #include <stdio.h>
> > typedef unsigned int u32;
> >
> > typedef u32 uint32_t;
> > typedef u32 uint32_t;
> >
> > int main(void) {
> > uint32_t test = 0;
> > printf("%u\n", test);
> > return 0;
> > }
> > $
> > $ powerpc-linux-gnu-gcc -o test test.c
> > test.c:5:13: error: redefinition of typedef 'uint32_t'
> > test.c:4:13: note: previous declaration of 'uint32_t' was here
>
> And I meant to add:
>
> $ powerpc-linux-gnu-gcc --version
> powerpc-linux-gnu-gcc (Sourcery G++ Lite 2010.09-55) 4.5.1
> Copyright (C) 2010 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> So, yeah, its really old.
>
> I'll get a newer one and test it.
I downloaded this version from denx.de (thank you, Wolfgang):
$ powerpc-linux-gcc --version
powerpc-linux-gcc (GCC) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Its still dated but its the best prebuilt version that I could find easily
available. With this version, the kernel (ppc6xx_defconfig) built without
issue.
Thanks to all who helped me through this.
To Ben or whoever, I think the original patch is still worth applying even
if it isn't critical.
Thanks,
Mark
--
next prev parent reply other threads:[~2018-03-31 2:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 21:54 [PATCH] powerpc/boot: Remove duplicate typedefs from libfdt_env.h Mark Greer
2018-03-19 8:53 ` Christophe LEROY
2018-03-19 16:02 ` Mark Greer
2018-03-19 17:35 ` christophe leroy
2018-03-19 23:55 ` Oliver
2018-03-30 2:22 ` Mark Greer
2018-03-30 2:26 ` Mark Greer
2018-03-31 2:42 ` Mark Greer [this message]
2018-04-03 16:03 ` Michael Ellerman
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=20180331024229.GA18304@animalcreek.com \
--to=mgreer@animalcreek.com \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oohall@gmail.com \
--cc=paulus@samba.org \
/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.
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).