Re: [win-pv-devel] [PATCH] Add a user mode library wrapper for XENIFACE IOCTLs

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: Paul Durrant
> Sent: 12 July 2018 09:05
> To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>; 'Marek Marczykowski-Górecki'
> <marmarek@xxxxxxxxxxxxxxxxxxxxxx>
> Cc: win-pv-devel@xxxxxxxxxxxxxxxxxxxx; Rafal Wojdyla
> <omeg@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: RE: [win-pv-devel] [PATCH] Add a user mode library wrapper for
> XENIFACE IOCTLs
> 
> > -----Original Message-----
> [snip]
> >
> > I tried building the new code but I have the same problem. Unfortunately I
> > have the same problem building master. So it appears that something in
> the
> > latest version of Visual Studio has completely borked the xeniface build.
> > Other drivers seem to be fine, but without meaningful error messages it
> may
> > take me some time to figure out what on earth Is going on.
> >
> 
> The issue appears to be across all drivers if I do fresh clones so I can only
> assume my environment is totally screwed after attempting to update to the
> latest vs2017. I'm going to re-install everything and see if I can make it 
> work.
> 

I think I've got to the bottom of this and the issue is running the build on 
Windows 10 1803 (and may be specific to having the bash subsystem enabled)...

It appears that Microsoft made NTFS case sensitive in 1803 with no global way 
of turning this off. Visual studio generates various pathnames with incorrect 
case and so, whereas this was fine with a case insensitive file system, it now 
completely breaks things.
Still looking for a workaround.

  Paul


>   Paul
_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/win-pv-devel