From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Masroor Vettuparambil <Masroor.Vettuparambil@exar.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: xen build error on gcc v4.5.0
Date: Wed, 18 Aug 2010 11:12:51 -0700 [thread overview]
Message-ID: <4C6C22A3.2030709@goop.org> (raw)
In-Reply-To: <78C9135A3D2ECE4B8162EBDCE82CAD7706ACAB3B@nekter>
On 08/18/2010 03:24 AM, Masroor Vettuparambil wrote:
> I got the below error when I do a 'make world' in xen-testing.hg . The kernel is 2.6.31.14. gcc version is 4.5.0.
> It is working with gcc v4.3.0
> Btw I thought the default kernel in xen-testing.hg is 2.6.32.x, but it is still 2.6.31.x.
>
> .............
>
> LD drivers/xen/blktap/blktap.o
> LD drivers/xen/blktap/built-in.o
> CC drivers/xen/netback/netback.o
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c: In function ânet_rx_actionâ:
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:495:32: error: storage size of ârx_mclâ isnât constant
Looks like a gcc bug. Older gccs can compute __RING_SIZE() as a
compile-time constant, but gcc 4.5.0 apparently isn't doing that. It
is, admittedly, a very complex expression, but gcc shouldn't regress
like this. I'm not sure how to work around it.
J
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:496:27: error: storage size of ârx_mmuâ isnât constant
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:497:32: error: storage size of âgrant_trans_opâ isnât constant
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:498:28: error: storage size of âgrant_copy_opâ isnât constant
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:500:13: error: storage size of ânotify_listâ isnât constant
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:501:30: error: storage size of âmetaâ isnât constant
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:529:2: warning:type defaults to âintâ in type name
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:529:2: warning:type defaults to âintâ in type name
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:529:2: error: size of unnamed array is negative
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:534:3: warning: type defaults to âintâ in type name
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:534:3: warning: type defaults to âintâ in type name
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:534:3: error: size of unnamed array is negative
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:548:3: warning: type defaults to âintâ in type name
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:548:3: warning: type defaults to âintâ in type name
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:548:3: error: size of unnamed array is negative
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:557:3: warning: type defaults to âintâ in type name
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:557:3: warning: type defaults to âintâ in type name
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:557:3: error: size of unnamed array is negative
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:569:2: warning: type defaults to âintâ in type name
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:569:2: warning: type defaults to âintâ in type name
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:569:2: error: size of unnamed array is negative
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:501:30: warning: unused variable âmetaâ
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:500:13: warning: unused variable ânotify_listâ
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:498:28: warning: unused variable âgrant_copy_opâ
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:497:32: warning: unused variable âgrant_trans_opâ
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:496:27: warning: unused variable ârx_mmuâ
> /home/xen/xen-4.0-testing.hg/linux-2.6-pvops.git/drivers/xen/netback/netback.c:495:32: warning: unused variable ârx_mclâ
> make[9]: *** [drivers/xen/netback/netback.o] Error 1
> make[8]: *** [drivers/xen/netback] Error 2
> make[7]: *** [drivers/xen] Error 2
> make[6]: *** [drivers] Error 2
> make[5]: *** [sub-make] Error 2
> make[4]: *** [all] Error 2
>
>
> Thanks,
> Masroor
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2010-08-18 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 10:24 xen build error on gcc v4.5.0 Masroor Vettuparambil
2010-08-18 18:12 ` Jeremy Fitzhardinge [this message]
2010-08-18 19:44 ` M A Young
2010-08-18 19:55 ` Keir Fraser
2010-08-18 23:07 ` Jeremy Fitzhardinge
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=4C6C22A3.2030709@goop.org \
--to=jeremy@goop.org \
--cc=Masroor.Vettuparambil@exar.com \
--cc=xen-devel@lists.xensource.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.
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.