From: Ian Campbell <Ian.Campbell@citrix.com>
To: Olaf Hering <olaf@aepfle.de>, Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "Xu, Quan" <quan.xu@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: stubdom vtpm build failure in staging
Date: Thu, 29 Jan 2015 10:46:32 +0000 [thread overview]
Message-ID: <1422528392.30641.24.camel@citrix.com> (raw)
In-Reply-To: <20150129102736.GA1106@aepfle.de>
On Thu, 2015-01-29 at 11:27 +0100, Olaf Hering wrote:
> On Thu, Jan 29, Olaf Hering wrote:
>
> > Looks like old gcc can not handle two typedefs?
>
> Yes, this fails already:
>
> typedef unsigned char BYTE;
> typedef unsigned char BYTE;
> void f(int *v) { *v *= *v; }
>
> t.c:2:23: error: redefinition of typedef 'BYTE'
> t.c:1:23: note: previous declaration of 'BYTE' was here
This compiles for me on Debian with gcc 4.7.2-5.
I'm honestly not sure what the C standard says about duplicate but
identical typedefs -- Ian?
Ian.
next prev parent reply other threads:[~2015-01-29 10:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 15:08 stubdom vtpm build failure in staging Olaf Hering
2015-01-28 15:13 ` Xu, Quan
2015-02-11 15:20 ` Olaf Hering
2015-02-12 16:56 ` Xu, Quan
2015-02-12 17:24 ` Xu, Quan
2015-02-12 17:40 ` Andrew Cooper
2015-02-13 2:07 ` Xu, Quan
2015-02-25 13:54 ` Ian Campbell
2015-02-27 15:07 ` Xu, Quan
2015-03-11 10:51 ` Ian Campbell
2015-03-12 1:46 ` Xu, Quan
2015-03-12 9:42 ` Ian Campbell
2015-03-12 15:44 ` Xu, Quan
2015-03-13 13:30 ` Olaf Hering
2015-03-13 15:39 ` Xu, Quan
2015-01-28 15:24 ` Ian Campbell
2015-01-29 7:34 ` Xu, Quan
2015-01-29 8:27 ` Olaf Hering
2015-01-29 9:22 ` Xu, Quan
2015-01-29 9:36 ` Olaf Hering
2015-01-29 10:27 ` Olaf Hering
2015-01-29 10:46 ` Ian Campbell [this message]
2015-01-30 8:09 ` Olaf Hering
2015-01-30 10:39 ` Ian Campbell
2015-01-30 11:03 ` Jan Beulich
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=1422528392.30641.24.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--cc=quan.xu@intel.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.