From: Tamar Christina <Tamar.Christina@arm.com>
To: mizo 91 <mizo91@gmail.com>,
Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: RE: CreateProcess No such file or directory
Date: Tue, 20 Sep 2022 22:27:37 +0000 [thread overview]
Message-ID: <VI1PR08MB5325BAA6DE3DED80E4CB1F1FFF4C9@VI1PR08MB5325.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAGt5VgGCvVm-2=gdv87XS8DNqLfu-KkcjqhrbQPHAA_vA9fOaw@mail.gmail.com>
We'd mostly be guessing here, use strace or https://learn.microsoft.com/en-us/sysinternals/downloads/procmon to see which path is actually being accessed and why it failed.
Also check that you can run `as` correctly. This error can also happen if a dependency of `as.exe` isn't found during loading.
Cheers,
Tamar
> -----Original Message-----
> From: Gcc-help <gcc-help-bounces+tamar.christina=arm.com@gcc.gnu.org>
> On Behalf Of mizo 91 via Gcc-help
> Sent: Tuesday, September 20, 2022 1:17 PM
> To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
> Cc: gcc-help@gcc.gnu.org
> Subject: Re: CreateProcess No such file or directory
>
> According to Microsoft docs path length limitation for windows is 256. In my
> case its 143 chars. I think the problem might be related to how gcc driver is
> passing along unmarshalled arguments to its subprograms like as.exe.
> Suprisingly this works correctly if I enforce gcc driver to use preprocessor only
> by adding -E flag
>
> btw. I failed to previously mention that I'm using Mingw-W64 version
> provided kindly by niXman Binaries taken directly from official MinGW-W64
> builds:
> https://www.mingw-w64.org/downloads/#mingw-builds
> https://github.com/niXman/mingw-builds-binaries/releases
>
> R.
>
> wt., 20 wrz 2022 o 18:18 Richard Earnshaw
> <Richard.Earnshaw@foss.arm.com>
> napisał(a):
>
> >
> >
> > 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 22:27 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
2022-09-20 17:17 ` mizo 91
2022-09-20 22:27 ` Tamar Christina [this message]
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=VI1PR08MB5325BAA6DE3DED80E4CB1F1FFF4C9@VI1PR08MB5325.eurprd08.prod.outlook.com \
--to=tamar.christina@arm.com \
--cc=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).