Hmmm only thing i could think of:
- catch exit code of make
- if error and qemu is out of date WRT to your Xen, give a nice warning with
solution (how to update qemu tree)
Sunday, January 16, 2011, 2:49:53 AM, you wrote:
> On Sat, 2011-01-15 at 18:27 +0000, Sander Eikelenboom wrote:
>> Hello Ian,
>>
>> Thx, didn't think of it, shouldn't the build-system check for that ?
>> Or should i do a "make world" or something to force that ?
> The reason for not doing so is that it would potentially blow away any
> locally made changes.
> If someone can come up with a scheme (and a patch) which removes this
> danger then I think we'd all be interested.
> Ian.
>>
>> --
>> Sander
>>
>> Saturday, January 15, 2011, 7:07:51 PM, you wrote:
>>
>> > On Sat, 2011-01-15 at 16:27 +0000, Sander Eikelenboom wrote:
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> changeset: 22744:54e91dcae649
>> >>
>> >> make -j6 debug=y results in:
>> >>
>> >> CC i386-dm/xen_disk.o
>> >> /usr/src/new/xen-unstable.hg/tools/ioemu-dir/hw/xen_backend.c: In
>> >> function âxen_be_get_xendevâ:
>> >> /usr/src/new/xen-unstable.hg/tools/ioemu-dir/hw/xen_backend.c:211:
>> >> error: too few arguments to function âxc_evtchn_openâ
>> >> /usr/src/new/xen-unstable.hg/tools/ioemu-dir/hw/xen_backend.c:217:
>> >> warning: passing argument 1 of âxc_evtchn_fdâ makes pointer from
>> >> integer without a cast
>>
>> > Suggests that your qemu is out of date WRT to your Xen. Try:
>> > make tools/ioemu-dir-force-update
>>
>> > Ian.
>>
>>
>>
>>
--
Best regards,
Sander mailto:linux@xxxxxxxxxxxxxx
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home