From: Steven Chamberlain <steven@pyro.eu.org>
To: Mark Felder <feld@feld.me>
Cc: xen-devel@lists.xen.org
Subject: Re: Fwd: xenbusb_nop_confighook_cb timeout and cd issue
Date: Wed, 30 Jan 2013 17:11:21 +0000 [thread overview]
Message-ID: <20130130171117.GB2805@loongson.pyro.eu.org> (raw)
In-Reply-To: <op.wrqfds2c34t2sn@markf.office.supranet.net>
Hi,
On 10:14, Mark Felder wrote:
> I did try it and it didn't seem to make a difference. I was going to
> check with my contact and have him reconfirm that the patches
> actually made it into those RPMs but I haven't had time :(
Okay, thanks for the feedback.
Unfortunately as Andrew Cooper pointed out, that patch turns out to have
zero effect on the compiled code.
Whatever fixed this for me, with xenkernel41 4.1.3nb2 on NetBSD, is
some other, unexplained difference between NetBSD's builds and my own
local builds, of the same source, in what should be an essentially
identical chrooted build environment (GCC 4.5.3 (NetBSD nb2 20110806),
pkgsrc-2012Q4).
Somehow both of the XCP 1.6 builds had this problem too (GCC 4.1.2
20080704 (Red Hat 4.1.2-46)).
Debian's builds (GCC 4.7.1) seem to be unaffected, although they carry a
lot of patches as well.
Regards,
--
Steven Chamberlain
steven@pyro.eu.org
next prev parent reply other threads:[~2013-01-30 17:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AD92DFA-7153-4E79-B906-1CBEAAC6B6A3@sarenet.es>
[not found] ` <CACAFB0D-0EA1-44FB-8622-0C547B5F0FCE@sarenet.es>
[not found] ` <50F3A8F8.7050809@pyro.eu.org>
2013-01-17 7:36 ` Fwd: xenbusb_nop_confighook_cb timeout and cd issue Christoph Egger
[not found] ` <50F7A9E8.4030007@gmx.de>
2013-01-17 11:19 ` Andrew Cooper
2013-01-17 11:19 ` Steven Chamberlain
[not found] ` <50F7DE55.8060101@pyro.eu.org>
2013-01-17 14:35 ` Christoph Egger
[not found] ` <50F80C4C.7040905@gmx.de>
2013-01-17 14:50 ` Juergen Gross
[not found] ` <50F80FB2.4060908@ts.fujitsu.com>
2013-01-17 14:57 ` Andrew Cooper
2013-01-17 17:50 ` Mark Felder
2013-01-30 14:18 ` Steven Chamberlain
2013-01-30 16:14 ` Mark Felder
2013-01-30 17:11 ` Steven Chamberlain [this message]
2013-01-17 14:53 ` Mark Felder
[not found] ` <op.wq18zu1d34t2sn@markf.office.supranet.net>
2013-01-17 15:04 ` Steven Chamberlain
2013-01-17 15:07 ` Steven Chamberlain
[not found] ` <50F813CB.7050801@pyro.eu.org>
2013-01-17 15:24 ` Mark Felder
[not found] ` <7ba7ddf7-3034-4422-8eed-5299318454a9@email.android.com>
2013-01-17 15:56 ` Steven Chamberlain
[not found] ` <50F81F31.3070103@pyro.eu.org>
2013-01-17 18:53 ` Mark Felder
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=20130130171117.GB2805@loongson.pyro.eu.org \
--to=steven@pyro.eu.org \
--cc=feld@feld.me \
--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 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).