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:38:53 +0000 [thread overview]
Message-ID: <bug-106468-4-GVXt7wQGHq@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 #5 from cqwrteur <unlvsur at live dot com> ---
Created attachment 53378
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53378&action=edit
DOS cannot find stdlib.h
Another thing is about dos
z:\home\cqwrteur\toolchains\x86_64-w64-mingw32\i586-msdosdjgpp\i586-msdosdjgpp\include\c++\v1\cstdlib:75:15:
fatal error: stdlib.h: No such file or directory
75 | #include_next <stdlib.h>
| ^~~~~~~~~~
compilation terminated.
prev parent reply other threads:[~2022-07-28 20:38 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
2022-07-28 20:38 ` unlvsur at live dot com [this message]
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-GVXt7wQGHq@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).