All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kieran Mansley <kmansley@solarflare.com>
To: "Zhao, Yunfeng" <yunfeng.zhao@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: RE: compile error of HVM pv drivers
Date: Mon, 30 Jul 2007 15:05:19 +0100	[thread overview]
Message-ID: <1185804320.4287.53.camel@moonstone.uk.level5networks.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77AA3EF75@pdsmsx411.ccr.corp.intel.com>

On Mon, 2007-07-30 at 21:49 +0800, Zhao, Yunfeng wrote:
> >Does gcc 3.4.2 cope OK with the rest of the kernel?
> >There are many other uses of netif_tx_lock_bh() and so it would be
> >interesting to know if it's something about that function, or something
> >about the way it's used in this instance that triggers the error.

Any thoughts on that one?

> >Any other information you can give that would help reproduce this would
> >be of great assistance.  E.g. kernel source version, exactly which
> >distribution, exactly which gcc (e.g. is it a version that might have
> >been modified by a linux vendor), etc.
> [Yunfeng] The build was tried on a FC3 root fs with using the gcc of
> fc3,

Which one? :)  There were probably multiple versions.  E.g. the fc3 box
I have access to is using:
[~]$ gcc --version
gcc (GCC) 3.4.3 20050227 (Red Hat 3.4.3-22.fc3)

I've had a look in the Changelog for both GCC and the redhat RPM from
around that time (between 3.4.2-1.fc3 and 3.4.3-22.fc3) and can't see
anything obvious that would have fixed this, but sometimes these things
aren't obvious.  

If you can try the version of gcc that works for me, that would be
useful for ruling out it being something else that I'm doing that makes
it work:

http://rpmfind.net/linux/RPM/fedora/updates/3/i386/gcc-3.4.3-22.fc3.i386.html

Kieran

  reply	other threads:[~2007-07-30 14:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30  9:28 compile error of HVM pv drivers Zhao, Yunfeng
2007-07-30  9:52 ` Keir Fraser
2007-07-30  9:58 ` Kieran Mansley
2007-07-30 10:13   ` Mats Petersson
2007-07-30 12:43   ` Zhao, Yunfeng
2007-07-30 13:42     ` Kieran Mansley
2007-07-30 13:49       ` Zhao, Yunfeng
2007-07-30 14:05         ` Kieran Mansley [this message]
2007-07-30 14:15           ` Zhao, Yunfeng
2007-07-30 14:22           ` Zhao, Yunfeng
2007-07-30 14:24             ` Kieran Mansley
2007-07-30 14:32               ` Zhao, Yunfeng
2007-07-30 14:39               ` Zhao, Yunfeng
2007-07-30 14:42                 ` Keir Fraser
2007-07-30 14:47                 ` Kieran Mansley
2007-07-30 14:51                   ` Keir Fraser
2007-07-30 15:02                     ` Zhao, Yunfeng
2007-07-30 15:05                       ` Keir Fraser
2007-07-30 15:38                         ` Zhao, Yunfeng
2007-07-30 15:42                           ` Kieran Mansley
2007-07-30 16:42                             ` Keir Fraser
2007-07-30 14:54                   ` Kieran Mansley

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=1185804320.4287.53.camel@moonstone.uk.level5networks.com \
    --to=kmansley@solarflare.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunfeng.zhao@intel.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.