On Wed, Feb 11, 2015 at 01:29:53PM +, Peter Maydell wrote:
> On 11 February 2015 at 12:33, Michael S. Tsirkin wrote:
> > On Wed, Feb 11, 2015 at 02:12:35AM +, Peter Maydell wrote:
> >> On 9 February 2015 at 19:56, Michael S. Tsirkin wrote:
> >> > +rm -rf "$output/standard-headers/linux"
>
On 11 February 2015 at 12:33, Michael S. Tsirkin wrote:
> On Wed, Feb 11, 2015 at 02:12:35AM +, Peter Maydell wrote:
>> On 9 February 2015 at 19:56, Michael S. Tsirkin wrote:
>> > +rm -rf "$output/standard-headers/linux"
>> > +mkdir -p "$output/standard-headers/linux"
>> > +for f in $tmpdir/i
On Wed, Feb 11, 2015 at 02:12:35AM +, Peter Maydell wrote:
> On 9 February 2015 at 19:56, Michael S. Tsirkin wrote:
> > +rm -rf "$output/standard-headers/linux"
> > +mkdir -p "$output/standard-headers/linux"
> > +for f in $tmpdir/include/linux/virtio*h; do
> > +header=$(expr "$f" : '.*/\(.
On Wed, Feb 11, 2015 at 03:46:20AM +, Peter Maydell wrote:
> On 11 February 2015 at 02:50, Chen, Tiejun wrote:
> > On 2015/2/11 10:03, Peter Maydell wrote:
> >> The linux-headers/ directory contains header files which can only
> >> validly be included if the host we're compiling on is Linux. S
On 2015/2/11 11:46, Peter Maydell wrote:
On 11 February 2015 at 02:50, Chen, Tiejun wrote:
On 2015/2/11 10:03, Peter Maydell wrote:
The linux-headers/ directory contains header files which can only
validly be included if the host we're compiling on is Linux. Some
of them will cause compile fai
On 11 February 2015 at 02:50, Chen, Tiejun wrote:
> On 2015/2/11 10:03, Peter Maydell wrote:
>> The linux-headers/ directory contains header files which can only
>> validly be included if the host we're compiling on is Linux. Some
>> of them will cause compile failures on OSX or Windows if they
>>
On 2015/2/11 10:03, Peter Maydell wrote:
On 11 February 2015 at 01:36, Chen, Tiejun wrote:
On 2015/2/10 3:56, Michael S. Tsirkin wrote:
It doesn't make sense to copy values manually:
the only issue with getting headers from linux
seems to be dealing with linux/types, we
can easily fix that au
On 9 February 2015 at 19:56, Michael S. Tsirkin wrote:
> +rm -rf "$output/standard-headers/linux"
> +mkdir -p "$output/standard-headers/linux"
> +for f in $tmpdir/include/linux/virtio*h; do
> +header=$(expr "$f" : '.*/\(.*\)');
> +sed -e 's/__u\([0-9][0-9]*\)/uint\1_t/g' \
> +-e 's
On 11 February 2015 at 01:36, Chen, Tiejun wrote:
> On 2015/2/10 3:56, Michael S. Tsirkin wrote:
>>
>> It doesn't make sense to copy values manually:
>> the only issue with getting headers from linux
>> seems to be dealing with linux/types, we
>> can easily fix that automatically while importing.
On 2015/2/10 3:56, Michael S. Tsirkin wrote:
It doesn't make sense to copy values manually:
the only issue with getting headers from linux
seems to be dealing with linux/types, we
can easily fix that automatically while importing.
Signed-off-by: Michael S. Tsirkin
---
FYI this is what I propos
It doesn't make sense to copy values manually:
the only issue with getting headers from linux
seems to be dealing with linux/types, we
can easily fix that automatically while importing.
Signed-off-by: Michael S. Tsirkin
---
FYI this is what I propose instead of the recently
suggested
virtio:
11 matches
Mail list logo