From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: mizo 91 <mizo91@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: CreateProcess No such file or directory
Date: Tue, 20 Sep 2022 17:18:07 +0100 [thread overview]
Message-ID: <a03afdf3-9f77-c19c-9bf4-4117a626ecdb@foss.arm.com> (raw)
In-Reply-To: <CAGt5VgF4tzCJMmbpu-Bq7ySQHdA_HuwbaaYJX7WSD=D4Yp068A@mail.gmail.com>
On 20/09/2022 17:02, mizo 91 via Gcc-help wrote:
> Hello,
>
> I'm having trouble compiling simple test program on windows 10 with long
> list of includes provided via '@response_file' argument
>
> The full error is:
>
> gcc.exe: fatal error: cannot execute
> 'C:/Tools/x86_64-12.2.0-release-win32-seh-rt_v10-rev0/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/12.2.0/../../../../x86_64-w64-mingw32/bin/as.exe':
> CreateProcess: No such file or directory
>
> compilation terminated.
>
> Above path to the assembler program is valid therefore I don't understand
> what is the issue here?
>
> You can try to recreate the problem by compiling simple main.c file with
> nothing in it but main function using command:
> gcc @includes.txt main.c
>
> I assume it has something to do with windows 32k CreateProcess command
> length limitation? But isn't that the reason why respone files were
> invented?
>
> Regards,
> Filip
I'm by no means a windows expert, but I wonder if this might be related
to the length of the path to the assembler and that it's somehow getting
truncated.
R.
next prev parent reply other threads:[~2022-09-20 16:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 16:02 mizo 91
2022-09-20 16:18 ` Richard Earnshaw [this message]
2022-09-20 17:17 ` mizo 91
2022-09-20 22:27 ` Tamar Christina
2022-09-21 2:42 ` fedor_qd
2022-09-21 15:27 ` mizo 91
2022-09-21 15:41 ` Tom Kacvinsky
2022-09-26 6:58 ` Re[2]: " fedor_qd
2022-09-22 6:44 ` LIU Hao
2022-09-22 7:35 ` mizo 91
2022-09-22 9:46 ` LIU Hao
2022-09-22 14:55 ` mizo 91
2022-09-22 16:04 ` LIU Hao
2022-09-22 16:50 ` mizo 91
2022-09-23 17:40 ` Xi Ruoyao
2022-09-23 21:11 ` mizo 91
2022-09-24 5:13 ` Xi Ruoyao
2022-09-24 9:28 ` mizo 91
2022-09-24 9:51 ` Xi Ruoyao
2022-09-24 10:20 ` Jonathan Wakely
2022-09-23 17:14 ` David Brown
2022-09-23 20:55 ` mizo 91
2022-09-22 8:19 ` Jonathan Wakely
2022-09-22 8:42 ` Jonathan Wakely
2022-09-22 9:48 ` LIU Hao
2022-09-22 9:50 ` mizo 91
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a03afdf3-9f77-c19c-9bf4-4117a626ecdb@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=gcc-help@gcc.gnu.org \
--cc=mizo91@gmail.com \
/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.
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).