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

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: 'Marek Marczykowski-Górecki'
> [mailto:marmarek@xxxxxxxxxxxxxxxxxxxxxx]
> Sent: 12 July 2018 17:05
> To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
> Cc: win-pv-devel@xxxxxxxxxxxxxxxxxxxx; Rafal Wojdyla
> <omeg@xxxxxxxxxxxxxxxxxxxxxx>
> Subject: Re: [win-pv-devel] [PATCH] Add a user mode library wrapper for
> XENIFACE IOCTLs
> 
> On Thu, Jul 12, 2018 at 03:33:32PM +0000, Paul Durrant wrote:
> > > -----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.
> 
> Oh, that seems like a major change, I wouldn't expect it, not without a
> major announcement earlier. But bash subsystem might be related - are
> you starting a build from there? Try starting a build from cmd.
> 

I do start from cmd but it's too late by that point. The problem comes when the 
linux subsystem mounts NTFS and turns on case sensitivity. From that point on 
any subdir created under a checked out source repo (i.e. all the working 
directories used by visual studio) are created with the case sensitive 
attribute and that's what causes the breakage... because various things (like 
code analysis and inf2cat) use paths with incorrect case.
The workaround Is to create a /etc/wsl.conf file and populate it with the 
following section:

[automount]
enabled = true
options = "case=off"

That way the next time the linux subsystem starts it leaves the case 
sensitivity of NTFS alone and freshly checked out repos start to build again.

Now I can have a proper look at your patch :-)

  Paul

> --
> Best Regards,
> Marek Marczykowski-Górecki
> Invisible Things Lab
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/win-pv-devel