9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Amavect <amavect@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Re: [PATCH] drawterm: get 64-bit windows to work
Date: Sun, 15 May 2022 15:56:06 -0500	[thread overview]
Message-ID: <20220515155606.1f4dfa76@spruce.localdomain> (raw)
In-Reply-To: <7ef02704-7dce-4005-b179-be9f491b647f@sirjofri.de>

On Sun, 15 May 2022 15:44:42 +0000 (UTC)
sirjofri <sirjofri+ml-9front@sirjofri.de> wrote:

> However, Make.win64 mentions that I can set MING to nothing when not 
> cross-compiling since it would just use gcc then. I tried it, but it 
> failed at some #include (I think it was direct.h). It is possible
> that it uses the "other" gcc version I installed on cygwin which
> tries to find libraries that aren't installed.

MSYS2's mingw64 environment requires the MING prefix to be empty
due to some programs (like windres) not having a prefix.
gcc and $(MING)gcc are aliases in that environment.
(MSYS2 is basically Cygwin but with pacman.)
Cygwin's unprefixed gcc targets its posix emulation dll,
so you'd always want to use the prefix to cross-compile.
It might also be missing parts of the win32 api.
Different gccs can have different default include directories.
It's confusing.

Thanks,
Amavect

      parent reply	other threads:[~2022-05-15 21:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07  2:13 [9front] " Amavect
2022-05-14 21:48 ` [9front] " Amavect
2022-05-14 22:38   ` ori
2022-05-15  7:01     ` sirjofri
2022-05-15 14:48       ` ori
2022-05-15 15:44         ` sirjofri
2022-05-15 15:47           ` ori
2022-05-15 15:57           ` sirjofri
2022-05-15 20:56           ` Amavect [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=20220515155606.1f4dfa76@spruce.localdomain \
    --to=amavect@gmail.com \
    --cc=9front@9front.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 NNTP newsgroup(s).