Re: Native compilation warnings, GNU Emacs 29.4, Windows 11

[Eli Zaretskii]

[Please use Reply All, to have the list CC'ed.]

> Date: Tue, 4 Feb 2025 16:37:42 +0100
> From: Bo Johansson <bo.johansson@brosarp.nu>
> 
> Hej!
> 
> My system is a bit messy!
> 
> Was GCC and/or Binutils and/or libgccjit also updated?  If so, do you
> know which of those were updated and to which versions?
> 
> I have attached a file with the date and versions of the packages in my 
> d:/MSYS64/var/lib/pacman/local
> directory. I believe that all are installed at the same time. 
> 
>  
> What do the following commands print?
> 
>   gcc --version
>   gcc --print-prog-name cc1
>   gcc --print-prog-name collect2
>   gcc --print-prog-name as
>   gcc --print-prog-name ld
>   gcc --print-search-dirs
>   ld --version
>   as --version
> 
> Please see the attached file. I have run the commands using the compile 
> command in Emacs.
> 
> Using the MSYS shell gives
> 
>      D:\MSYS64\home\bo>gcc --version
>      'gcc' is not recognized as an internal or external command, operable 
> program or batch file.

So gcc is not on PATH for some reason.

> I do not need the native compilation. It is OK for me to block the pop-up of 
> the buffer with the warnings.

Yes.

> Some silly questions:
> 
> An .elc file can be byte compiled or native compiled? (Yes)

Yes.

> Can Emacs use a combination of native compiled and byte compiled files.? (Yes)

Yes.

> How can I see how many of my file are native compiled?

"C-h f" for some function in the file will tell you.

>   02-01 23:50 mingw-w64-x86_64-libgccjit-14.2.0-2
>   02-01 23:50 mingw-w64-x86_64-gcc-14.2.0-2

This says you installed GCC 14.2.0 and its libgccjit library.

> gcc --version:
> gcc (MinGW-W64 x86_64-msvcrt-posix-seh, built by Brecht Sanders) 13.1.0
> Copyright (C) 2023 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

But this says that you have GCC 13.1.0 installed and on PATH.

So I think my initial guess was correct: you have a mixed
GCC/libgccjit installation which mixes different GCC versions.
Cleaning up your installation should solve the problem.