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

[Andrea Corallo]

Phillip Lord <phillip.lord@russet.org.uk> writes:

> Andrea Corallo <akrl@sdf.org> writes:
>
>> Phillip Lord <phillip.lord@russet.org.uk> writes:
>>
>>
>>>
>>> Compiling 
>>> c:/msys64/home/Administrator/emacs-upload/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/share/emacs/28.0.50/lisp/emacs-lisp/cl-lib.el...
>>> compiling to 
>>> c:/Users/Administrator/AppData/Roaming/.emacs.d/eln-cache/28.0.50-14889799/cl-lib-8b938900-d1df28b7.eln
>>> x86_64-w64-mingw32-gcc-10.2.0: fatal error: cannot execute 'as': 
>>> CreateProcess: No such file or directory
>>> compilation terminated.
>>
>> Mmmh ATM I don't know why the internal GCC driver is not finding as,
>> might be for one of these env vars [1]?
>>
>>>
>>> I've tried putting as.exe manually into the package but that isn't
>>> enough. as.exe doesn't seem to have any dll dependencies itself.
>>>
>>> Andrea what other tools does native-comp require to have around? Is
>>> there a good way to debug the compilation process, so I can work out
>>> what the file missing is?
>>
>> I'd say linker and assembler.
>>
>> I think if we don't solve with the mentioned env vars or we are unappy
>> with the solution these are really questions for jit@gcc.gnu.org.
>
>
> I've tried adding ld.exe and as.exe, and altering the path (at runtime
> which Eli says is bad).
>
> I am now getting this error message; it's different so that's obviously
> part of the problem.
>
>    Warning (comp): Debugger entered--Lisp error: (native-ice
> "c:/msys64/home/Administrator/emacs-upload/emacs-28..." "failed to
> compile" "c:/Users/Administrator/AppData/Roaming/.emacs.d/el..."
> "error invoking gcc driver") Disable showing Disable logging
>
>
> I'm try following up on jit@gcc as you suggest. They may well know what
> I need for a minimal functional install. Once I have that, I can work
> out how to achieve it in the package. At this rate, though, I fear that
> I am moving back to shipping half of msys.

Hi Phillip,

you should see the full error in the *Async-native-compile-log* buffer.

That said I'd suggest if possible to try to package the simplest
libgccjit "hello world" [1] to investigate what's needed for that to
run, collecting errors and debugging will be quicker, same for reporting
to the libgccjit mailing list in case.

Thanks for your effort!

  Andrea

[1] <https://gcc.gnu.org/onlinedocs/jit/intro/tutorial01.html>