Recent changeset breaks Xen/ia64 build

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Recent changeset breaks Xen/ia64 build

Dan Magenheimer
Hmmm... some changeset in -unstable in the last 24 hours has
badly broken the Xen/ia64 build.  From the cascade of
error messages, I suspect it is type-related.  I'll look
into it but if someone could point to the likely culprit,
I'd appreciate it.

Thanks,
Dan

_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

Re: Recent changeset breaks Xen/ia64 build

Ted Kaczmarek
On Wed, 2005-10-12 at 06:37 -0700, Magenheimer, Dan (HP Labs Fort
Collins) wrote:

> Hmmm... some changeset in -unstable in the last 24 hours has
> badly broken the Xen/ia64 build.  From the cascade of
> error messages, I suspect it is type-related.  I'll look
> into it but if someone could point to the likely culprit,
> I'd appreciate it.
>
> Thanks,
> Dan
>
> _______________________________________________
As well as my SMP Athlon spin, but UP P4 is fine.

  CC      drivers/xen/blktap/xenbus.o
drivers/xen/blktap/xenbus.c: In function `frontend_changed':
drivers/xen/blktap/xenbus.c:72: warning: passing arg 1 of
`xenbus_exists' from incompatible pointer type
drivers/xen/blktap/xenbus.c:72: error: too few arguments to function
`xenbus_exists'
drivers/xen/blktap/xenbus.c:73: warning: passing arg 1 of `xenbus_rm'
from incompatible pointer type
drivers/xen/blktap/xenbus.c:73: error: too few arguments to function
`xenbus_rm'
drivers/xen/blktap/xenbus.c:81: warning: passing arg 1 of
`xenbus_gather' from incompatible pointer type
drivers/xen/blktap/xenbus.c:102: warning: passing arg 1 of
`xenbus_transaction_end' makes pointer from integer without a cast
drivers/xen/blktap/xenbus.c:102: error: too few arguments to function
`xenbus_transaction_end'
drivers/xen/blktap/xenbus.c: In function `blkback_probe':
drivers/xen/blktap/xenbus.c:156: warning: passing arg 1 of
`xenbus_gather' from incompatible pointer type
drivers/xen/blktap/xenbus.c:165: warning: passing arg 1 of
`xenbus_exists' from incompatible pointer type
drivers/xen/blktap/xenbus.c:165: error: too few arguments to function
`xenbus_exists'


Regards,
Ted


_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

Re: Recent changeset breaks Xen/ia64 build

Keir Fraser
In reply to this post by Dan Magenheimer

On 12 Oct 2005, at 14:37, Magenheimer, Dan (HP Labs Fort Collins) wrote:

> Hmmm... some changeset in -unstable in the last 24 hours has
> badly broken the Xen/ia64 build.  From the cascade of
> error messages, I suspect it is type-related.  I'll look
> into it but if someone could point to the likely culprit,
> I'd appreciate it.

I removed u8/u16/u32 etc from the public interfaces and fiddled with
xen/types.h at the same time. Perhaps I've managed to break xen/types.h
for you?

  -- Keir


_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel
Reply | Threaded
Open this post in threaded view
|

RE: Recent changeset breaks Xen/ia64 build

Dan Magenheimer
In reply to this post by Dan Magenheimer
Thanks for the help.  I'm still not clear on how what
changed caused the cascading errors, but discovered
that two arch/ia64/vmx files have included public/xen.h
and removing that include fixes the problem.

I'll change this for the next ia64 push.

Dan

> -----Original Message-----
> From: Keir Fraser [mailto:[hidden email]]
> Sent: Wednesday, October 12, 2005 8:11 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: [hidden email]
> Subject: Re: [Xen-devel] Recent changeset breaks Xen/ia64 build
>
>
> On 12 Oct 2005, at 14:37, Magenheimer, Dan (HP Labs Fort
> Collins) wrote:
>
> > Hmmm... some changeset in -unstable in the last 24 hours has
> > badly broken the Xen/ia64 build.  From the cascade of
> > error messages, I suspect it is type-related.  I'll look
> > into it but if someone could point to the likely culprit,
> > I'd appreciate it.
>
> I removed u8/u16/u32 etc from the public interfaces and fiddled with
> xen/types.h at the same time. Perhaps I've managed to break
> xen/types.h
> for you?
>
>   -- Keir
>
>

_______________________________________________
Xen-devel mailing list
[hidden email]
http://lists.xensource.com/xen-devel