From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha@sourceware.org
Subject: Re: FW: several glibc build bugs on MinGW-w64
Date: Tue, 13 Oct 2020 17:53:58 -0300 [thread overview]
Message-ID: <dc1a2485-432f-ebbf-85e8-519e83784a7a@linaro.org> (raw)
In-Reply-To: <CH2PR02MB65220062156C791FB0DA340BB2040@CH2PR02MB6522.namprd02.prod.outlook.com>
On 13/10/2020 13:43, sotrdg sotrdg via Libc-alpha wrote:
> It looks the command line overflows the windows command line. Too long. Any way to get it around?
>
> Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
>
> From: sotrdg sotrdg<mailto:euloanty@live.com>
> Sent: Tuesday, October 13, 2020 12:32
> To: sotrdg sotrdg via Libc-alpha<mailto:libc-alpha@sourceware.org>
> Subject: several glibc build bugs on MinGW-w64
>
> I am building a x86_64-linux-gnu toolchain so I can build Linux programs on Win32 without wsl. I have finished building crt0. But other issues remain.
As I indicated on libc-help [1], glibc has no support or plan to work
to support mingw.
[1] https://sourceware.org/pipermail/libc-help/2020-October/005482.html
next prev parent reply other threads:[~2020-10-13 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 16:32 several glibc build bugs on MinGW-w64 sotrdg sotrdg via Libc-alpha
2020-10-13 16:43 ` FW: " sotrdg sotrdg via Libc-alpha
2020-10-13 20:53 ` Adhemerval Zanella via Libc-alpha [this message]
[not found] <CH2PR02MB652261928A76F3257DE01D20B2000@CH2PR02MB6522.namprd02.prod.outlook.com>
[not found] ` <xnmu0l1vg8.fsf@greed.delorie.com>
2020-10-17 10:31 ` sotrdg sotrdg via Libc-alpha
2020-10-17 10:46 ` sotrdg sotrdg via Libc-alpha
2020-10-17 10:50 ` sotrdg sotrdg via Libc-alpha
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/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc1a2485-432f-ebbf-85e8-519e83784a7a@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.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).