From: Eli Zaretskii <eliz@gnu.org>
To: Phillip Lord <phillip.lord@russet.org.uk>
Cc: emacs-devel@gnu.org, akrl@sdf.org
Subject: Re: [feature/native-comp] breakage on build
Date: Fri, 05 Feb 2021 23:04:19 +0200 [thread overview]
Message-ID: <8335yap6p8.fsf@gnu.org> (raw)
In-Reply-To: <87czxe45f8.fsf@russet.org.uk> (message from Phillip Lord on Fri, 05 Feb 2021 20:37:31 +0000)
> From: Phillip Lord <phillip.lord@russet.org.uk>
> Cc: akrl@sdf.org, emacs-devel@gnu.org
> Date: Fri, 05 Feb 2021 20:37:31 +0000
>
> I have checked the library paths as well as I know how (gcc
> --print-search-dirs). I have reformatted the output with some new lines
> to make it readable.
I'm not sure I understand: do these directories really exist, and do
they hold the libraries gcc is looking for? I mean these directories:
> ** Search paths (broken)
> gcc --print-search-dirs
> install: c:/Users/Administrator/Desktop/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/
> programs: =c:/Users/Administrator/Desktop/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/;c:/Users/Administrator/Desktop/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/bin/../lib/gcc/;c:/Users/Administrator/Desktop/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32/bin/x86_64-w64-mingw32/10.2.0/;c:/Users/Administrator/Desktop/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32/bin/
>
> libraries:
> =c:/Users/Administrator/Desktop/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/;
> c:/Users/Administrator/Desktop/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/bin/../lib/gcc/;
> c:/Users/Administrator/Desktop/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32/lib/x86_64-w64-mingw32/10.2.0/;
> c:/Users/Administrator/Desktop/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32/lib/../lib/;
> c:/Users/Administrator/Desktop/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../x86_64-w64-mingw32/10.2.0/;
> c:/Users/Administrator/Desktop/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../lib/;
> D:/a/_temp/msys/msys64/mingw64/x86_64-w64-mingw32/lib/x86_64-w64-mingw32/10.2.0/;
> D:/a/_temp/msys/msys64/mingw64/x86_64-w64-mingw32/lib/../lib/;
> c:/Users/Administrator/Desktop/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32/lib/;
> c:/Users/Administrator/Desktop/emacs-28.0.50-snapshot-feature_native-comp-windows-2021-02-04/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../;
> D:/a/_temp/msys/msys64/mingw64/x86_64-w64-mingw32/lib/
If they do exist, does it mean you duplicated the entire MinGW GCC
installation under the same directory that is the parent of the
Emacs's bin/ directory?
What does the following command produce?
gcc -print-file-name=crtbegin.o
> The equivalent version for an Emacs run from mingw64 shell (which works
> and JIT compiles), I get this.
>
>
>
> ** Search paths (working)
>
> gcc --print-search-dirs
> install: C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/
> programs: =C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/;C:/msys64/mingw64/bin/../lib/gcc/;C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw324/10.2.0/../../../../x86_64-w64-mingw32/bin/x86_64-w64-mingw32/10.2.0/;C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32/bin/
>
> libraries:
> =C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/;
> C:/msys64/mingw64/bin/../lib/gcc/;
> C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32/lib/x86_64-w64-mingw32/10.2.0/;
> C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32/lib/../lib/;
> C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../x86_64-w64-mingw32/10.2.0/;
> C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../lib/;
> D:/a/_temp/msys/msys64/mingw64/x86_64-w64-mingw32/lib/x86_64-w64-mingw32/10.2.0/;D:/a/_temp/msys/msys64/mingw64/x86_64-w64-mingw32/lib/../lib/;
> C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32/lib/;
> C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../;D:/a/_temp/msys/msys64/mingw64/x86_64-w64-mingw32/lib/
Does the mingw64 shell set some GCC-related environment variables,
like COMPILER_PATH or LIBRARY_PATH?
Alternatively, could it be that under the mingw64 shell Emacs invokes
a different copy of gcc/libgccjit, the one that is in its "normal"
installation tree and not in the Emacs tree?
next prev parent reply other threads:[~2021-02-05 21:04 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 10:37 [feature/native-comp] breakage on build Phillip Lord
2021-01-30 13:26 ` akrl--- via Emacs development discussions.
2021-01-30 14:40 ` phillip.lord
2021-01-30 15:01 ` phillip.lord
2021-01-30 16:21 ` Eli Zaretskii
2021-01-30 16:38 ` Eli Zaretskii
2021-01-30 17:06 ` Eli Zaretskii
2021-01-30 17:19 ` phillip.lord
2021-01-30 19:44 ` akrl--- via Emacs development discussions.
2021-01-30 19:58 ` Eli Zaretskii
2021-01-30 20:17 ` akrl--- via Emacs development discussions.
2021-01-31 15:29 ` Eli Zaretskii
2021-02-01 11:01 ` akrl--- via Emacs development discussions.
2021-02-01 15:25 ` Eli Zaretskii
2021-02-01 16:20 ` akrl--- via Emacs development discussions.
[not found] ` <831rdz7mf5.fsf@gnu.org>
2021-02-01 19:01 ` akrl--- via Emacs development discussions.
2021-02-01 19:06 ` Phillip Lord
2021-02-01 19:36 ` Eli Zaretskii
2021-02-01 19:37 ` Stefan Monnier
2021-02-01 20:33 ` akrl--- via Emacs development discussions.
2021-02-02 20:26 ` akrl--- via Emacs development discussions.
2021-02-02 20:29 ` Eli Zaretskii
2021-02-03 12:37 ` akrl--- via Emacs development discussions.
2021-02-03 16:36 ` Phillip Lord
2021-02-03 20:27 ` akrl--- via Emacs development discussions.
2021-02-04 3:31 ` Eli Zaretskii
2021-02-04 14:39 ` Phillip Lord
2021-02-04 15:31 ` Eli Zaretskii
2021-02-04 15:52 ` Phillip Lord
2021-02-04 16:24 ` Eli Zaretskii
2021-02-04 20:24 ` Óscar Fuentes
2021-02-04 20:44 ` Eli Zaretskii
2021-02-04 22:08 ` Óscar Fuentes
2021-02-05 11:50 ` Eli Zaretskii
2021-02-05 14:47 ` Óscar Fuentes
2021-02-05 21:29 ` Phillip Lord
2021-02-05 22:56 ` Óscar Fuentes
2021-02-06 13:15 ` Phillip Lord
2021-02-07 2:52 ` Óscar Fuentes
2021-02-07 18:56 ` Phillip Lord
2021-02-07 19:38 ` Óscar Fuentes
2021-02-07 19:49 ` Eli Zaretskii
2021-02-07 20:33 ` Stefan Monnier
2021-02-07 21:23 ` Óscar Fuentes
2021-02-07 22:23 ` Phillip Lord
2021-02-07 22:21 ` Phillip Lord
2021-02-07 23:38 ` Óscar Fuentes
2021-02-08 12:03 ` Phillip Lord
2021-02-06 7:32 ` Eli Zaretskii
2021-02-04 16:22 ` Andrea Corallo via Emacs development discussions.
2021-02-04 21:07 ` Phillip Lord
2021-02-04 23:32 ` Andrea Corallo via Emacs development discussions.
2021-02-05 10:05 ` Phillip Lord
2021-02-05 11:35 ` Eli Zaretskii
2021-02-05 20:37 ` Phillip Lord
2021-02-05 21:04 ` Eli Zaretskii [this message]
2021-02-05 21:50 ` Phillip Lord
2021-02-06 7:45 ` Eli Zaretskii
2021-02-06 12:58 ` Phillip Lord
2021-02-06 13:45 ` Eli Zaretskii
2021-02-07 19:11 ` Phillip Lord
2021-02-08 9:32 ` Andrea Corallo via Emacs development discussions.
2021-02-08 12:08 ` Phillip Lord
2021-02-08 14:28 ` Andrea Corallo via Emacs development discussions.
2021-02-08 14:47 ` Phillip Lord
2021-02-08 15:14 ` Andrea Corallo via Emacs development discussions.
2021-02-08 21:38 ` Stefan Monnier
2021-02-09 8:25 ` Andrea Corallo via Emacs development discussions.
2021-02-09 22:38 ` Phillip Lord
2021-02-10 8:44 ` Andrea Corallo via Emacs development discussions.
2021-02-10 14:04 ` Stefan Monnier
2021-02-10 14:23 ` Andrea Corallo via Emacs development discussions.
2021-02-15 19:17 ` Phillip Lord
2021-02-10 15:16 ` Eli Zaretskii
2021-02-10 20:41 ` Andrea Corallo via Emacs development discussions.
2021-02-11 14:11 ` Eli Zaretskii
2021-02-11 14:51 ` Andrea Corallo via Emacs development discussions.
2021-02-11 15:24 ` Eli Zaretskii
2021-02-11 15:53 ` Andrea Corallo via Emacs development discussions.
2021-02-11 16:11 ` Stefan Monnier
2021-02-11 16:20 ` Andrea Corallo via Emacs development discussions.
2021-02-11 20:52 ` Andrea Corallo via Emacs development discussions.
2021-02-12 6:46 ` Eli Zaretskii
2021-02-10 21:23 ` Phillip Lord
2021-02-11 8:39 ` Andrea Corallo via Emacs development discussions.
2021-02-08 15:25 ` Eli Zaretskii
2021-02-08 15:23 ` Eli Zaretskii
2021-02-07 2:15 ` Óscar Fuentes
2021-02-07 4:14 ` Óscar Fuentes
2021-02-05 11:35 ` Andrea Corallo via Emacs development discussions.
2021-02-05 20:44 ` Phillip Lord
2021-02-05 7:28 ` Eli Zaretskii
2021-01-30 20:21 ` Óscar Fuentes
2021-01-30 22:06 ` Stefan Monnier
2021-01-30 22:23 ` Óscar Fuentes
2021-01-30 22:53 ` Stefan Monnier
2021-02-02 0:27 ` Andy Moreton
2021-02-02 9:11 ` akrl--- via Emacs development discussions.
-- strict thread matches above, loose matches on Subject: below --
2021-02-01 18:39 Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8335yap6p8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=akrl@sdf.org \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).