From: Paul J THACKER <paul.thacker@st.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: compilation errors
Date: Fri, 06 Jun 2008 16:23:00 -0000 [thread overview]
Message-ID: <484964B2.4030902@st.com> (raw)
In-Reply-To: <20080606072624.GD422@lunn.ch>
Andrew Lunn wrote:
> On Thu, Jun 05, 2008 at 11:58:00AM -0700, Paul J THACKER wrote:
>> Hi,
>>
>> Trying to compile the latest from CVS on Suse 10.1:
>>
>> In file included from /usr/include/linux/usb.h:4,
>> from
>> ../../../../../../../packages/io/usb/slave/current/host/usbhost.c:87:
>> /usr/include/linux/mod_devicetable.h:174: error: expected
>> specifier-qualifier-list before ?__u8?
>> /usr/include/linux/mod_devicetable.h:204: error: expected
>> specifier-qualifier-list before ?__u16?
>> /usr/include/linux/mod_devicetable.h:251: error: expected
>> specifier-qualifier-list before ?__u16?
>> In file included from
>> ../../../../../../../packages/io/usb/slave/current/host/usbhost.c:88:
>> /usr/include/linux/usbdevice_fs.h:49: error: expected ?:?, ?,?, ?;?, ?}?
>> or ?__attribute__? before ?*? token
>> /usr/include/linux/usbdevice_fs.h:56: error: expected ?:?, ?,?, ?;?, ?}?
>> or ?__attribute__? before ?*? token
>>
>> etc...
>>
>> Looks like linux kernel header mismatch, but I'm not sure. Any ideas?
>
> Do you plan to use USB? If not, ignore it. It should be the last thing
> in the host tools that is built, so it should of built all the other
> host tools you need for building eCos. So just ignore it. If you do
> plan to use USB, let me know which Linux kernel version you have and i
> can take a look.
>
> Andrew
Thanks for the reply. I don't plan to use usb, at least not initially.
I'll ignore it.
Regards,
Paul
prev parent reply other threads:[~2008-06-06 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 18:56 Paul J THACKER
2008-06-06 7:26 ` Andrew Lunn
2008-06-06 16:23 ` Paul J THACKER [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=484964B2.4030902@st.com \
--to=paul.thacker@st.com \
--cc=andrew@lunn.ch \
--cc=ecos-devel@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).