public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: "gmail Vladimir Koković" <vladimir.kokovic@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Advice on communication regarding mingw cross build problems
Date: Wed, 25 Nov 2020 22:24:15 -1000	[thread overview]
Message-ID: <CAF1jjLvspb9Qy9n+qOa+9jV9YQAKdHZnt-ejko2ba758_Dmh0g@mail.gmail.com> (raw)
In-Reply-To: <2a34dec0-99e7-a6a7-e591-3f81e3831665@gmail.com>

Go to mingw-w64.sf.net

On Wed, Nov 18, 2020, 12:56 AM gmail Vladimir Koković via Gcc-help <
gcc-help@gcc.gnu.org> wrote:

> I would ask someone to tell me how and with whom I can try to solve
> mingw cross compile build problems so that it is like linux build.
> The main reason why I seek advice is my tendency not to be a bugs list.
>
>
> Vladimir Koković, DP senior(70),
>
> Serbia, Belgrade, 18.November 2020
>
>

      reply	other threads:[~2020-11-26  8:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 10:54 gmail Vladimir Koković
2020-11-26  8:24 ` NightStrike [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=CAF1jjLvspb9Qy9n+qOa+9jV9YQAKdHZnt-ejko2ba758_Dmh0g@mail.gmail.com \
    --to=nightstrike@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=vladimir.kokovic@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).