public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/106468] gcc does not run in wine
Date: Thu, 28 Jul 2022 20:34:39 +0000	[thread overview]
Message-ID: <bug-106468-4-0iI3IlC0Kv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106468-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106468

--- Comment #4 from cqwrteur <unlvsur at live dot com> ---
(In reply to cqwrteur from comment #3)
> Created attachment 53377 [details]
> -v

hmhm. i just found out the issue. I did not link to -lntdll. the problem is
that when GCC runs in wine, some part of its command would not display
correctly if the length is too long.

  parent reply	other threads:[~2022-07-28 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 19:56 [Bug other/106468] New: " unlvsur at live dot com
2022-07-28 19:58 ` [Bug other/106468] " pinskia at gcc dot gnu.org
2022-07-28 19:59 ` pinskia at gcc dot gnu.org
2022-07-28 20:29 ` unlvsur at live dot com
2022-07-28 20:34 ` unlvsur at live dot com [this message]
2022-07-28 20:38 ` unlvsur at live dot com

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=bug-106468-4-0iI3IlC0Kv@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).