Re: [feature/native-comp] breakage on build

[phillip . lord]

On 2021-01-30 14:40, phillip.lord@russet.org.uk wrote:
> On 2021-01-30 13:26, akrl--- via "Emacs development discussions." 
> wrote:
> > Phillip Lord <phillip.lord@russet.org.uk> writes:
> >
> > > I am getting a build breakage on native-comp. While I can build
> > > native-comp on windows in source, it seems to fail while using my
> > > packaging scripts. These use out-of-source builds which might be the
> > > problem.
> > >
> > > Backtrace is here. I've added a few "message"'s to
> > > `comp-compile-ctxt-to-file' so I could see the full paths. The 
> > > directory
> > > mentioned does exist but is empty.
> > >
> > > I am getting that there is something that isn't happy with windows
> > > paths, but that's a total guess.
> > >
> > > Phil
> >
> > Hi Phil,
> >
> > I tried just now an out of tree build on x86_64-pc-linux-gnu and it
> > worked.  This might confirm your idea of a Windows specific issue?
> >
> > Would be interesting to debug and see exactly what's the file that we
> > can't create and why.
>
>
> I will give it a go and see what I can find. I'd checked an OOS build
> on linux already, but I don't think I have done a "normal" one, that
> is not using my packaging scripts, on windows. Will try.


Actually, the error message appears to make from (and only from) 
make-temp-file-internal.

comp.c is nearly the only think that calls that function from c, so I'd 
guess that this is the culprit. I wonder if the windows drive letters 
("c:/msys64") use magic file handling.

Certainly

(make-temp-file-internal "c:/fred" nil "suf" nil)

raises the same error on linux (am afraid all my windows machines are 
inaccessible at the moment).

Phil