From: Mark Greer <mgreer@animalcreek.com>
To: Christophe LEROY <christophe.leroy@c-s.fr>
Cc: Mark Greer <mgreer@animalcreek.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Oliver O'Halloran <oohall@gmail.com>,
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: Mon, 19 Mar 2018 09:02:16 -0700 [thread overview]
Message-ID: <20180319160216.GD9670@animalcreek.com> (raw)
In-Reply-To: <e710d9d7-232b-6420-96a7-8167dd91b824@c-s.fr>
On Mon, Mar 19, 2018 at 09:53:09AM +0100, Christophe LEROY wrote:
>
>
> Le 16/03/2018 à 22:54, Mark Greer a écrit :
> >When building a uImage or zImage using ppc6xx_defconfig and some other
> >defconfigs, the following error occurs:
> >
> > BOOTCC arch/powerpc/boot/fdt.o
> > In file included from arch/powerpc/boot/fdt.c:51:0:
> > ../arch/powerpc/boot/libfdt_env.h:10:13: error: redefinition of typedef 'uint32_t'
> > ../arch/powerpc/boot/types.h:21:13: note: previous declaration of 'uint32_t' was here
> > ../arch/powerpc/boot/libfdt_env.h:11:13: error: redefinition of typedef 'uint64_t'
> > ../arch/powerpc/boot/types.h:22:13: note: previous declaration of 'uint64_t' was here
> > ../arch/powerpc/boot/Makefile:210: recipe for target 'arch/powerpc/boot/fdt.o' failed
> > make[2]: *** [arch/powerpc/boot/fdt.o] Error 1
> >
> >The problem is that commit 656ad58ef19e (powerpc/boot: Add OPAL console
> >to epapr wrappers) adds typedefs for uint32_t and uint64_t to type.h but
> >doesn't remove the pre-existing (and now duplicate) typedefs from
> >libfdt_env.h. Fix the error by removing the duplicat typedefs from
> >libfdt_env.h
> >
> >CC: David Gibson <david@gibson.dropbear.id.au>
> >CC: Oliver O'Halloran <oohall@gmail.com>
> >Signed-off-by: Mark Greer <mgreer@animalcreek.com>
> >---
> >Having said all of that, commit 656ad58ef19e (powerpc/boot: Add OPAL
> >console to epapr wrappers) went into mainline back in 2016 so, AFAICT,
> >this has been broken since then. That seems unlikely so I must be
> >missing something... Any ideas what that is?
>
> I just compiled uImage for ppc6xx_defconfig, and I don't get such error.
> I looked at what gcc -E outputs, u32 is defined twice but it doesn't seems
> to bother GCC.
>
> What version of GCC do you use ?
> I tried with 5.4.0 and 4.6.3, both seems to work.
>
> Christophe
Hi Christophe.
That's interesting. I would expect an error regardless of version.
I used an old 4.5.1 gcc that I had laying around (from denx, iirc).
I'll find a newer one and try it.
Either way, it seems to me that we should remove the duplicate definitions.
Do you agree?
Thanks,
Mark
--
next prev parent reply other threads:[~2018-03-19 16:02 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 [this message]
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
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=20180319160216.GD9670@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).