From: Robert Reif <reif@earthlink.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PATCH: fix usb-linux.c compile orror
Date: Tue, 30 Sep 2008 18:31:11 -0400 [thread overview]
Message-ID: <48E2A8AF.7070907@earthlink.net> (raw)
In-Reply-To: <48E23DAF.8070509@codemonkey.ws>
Anthony Liguori wrote:
> Vince Weaver wrote:
>>
>> On Mon, 29 Sep 2008, Anthony Liguori wrote:
>>> Robert Reif wrote:
>>>> RH9 system (2.4.20-31.9smp).
>>>
>>> Huh. I'm amazed it compiles with just that change on such an old
>>> kernel.
>>
>> I have similar problems compiling on a SuSE 10.1 system which really
>> isn't that old. Since I only use linux-user I'd been too lazy to
>> investigate the problem.
>>
>> Why should Qemu not build on older systems? I'd imagine that linux
>> 2.4 / 2.6 compatability would be easier to handle than linux /OSX
>> /Windows compatability.
>
> I think we should support 2.4 kernels FWIW. I'm just waiting for
> someone to send a patch that adds a configure check instead of
> breaking the build for newer kernels.
>
> I think the best way to do it would be to try and detect the right
> header files for usb pass through in configure, and disable
> usb-linux.c entirely if they aren't available.
>
> Regards,
>
> Anthony LIguori
>
>> Vince
>>
>>
The problem in this instance is that a structure that usb uses was
copied from a linux header file so the c file wasn't dependent on linux
headers. Unfortunately the c file wasn't changed to use the new structure.
prev parent reply other threads:[~2008-09-30 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 18:54 [Qemu-devel] PATCH: fix usb-linux.c compile orror Robert Reif
2008-09-29 16:13 ` Anthony Liguori
2008-09-30 0:54 ` Robert Reif
2008-09-30 1:38 ` Anthony Liguori
2008-09-30 14:12 ` Vince Weaver
2008-09-30 14:54 ` Anthony Liguori
2008-09-30 22:31 ` Robert Reif [this message]
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=48E2A8AF.7070907@earthlink.net \
--to=reif@earthlink.net \
--cc=qemu-devel@nongnu.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).