9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Re: [PATCH] drawterm: get 64-bit windows to work
Date: Sun, 15 May 2022 11:47:11 -0400	[thread overview]
Message-ID: <07C1BD919339382B9EEC14724F2C8367@eigenstate.org> (raw)
In-Reply-To: <7ef02704-7dce-4005-b179-be9f491b647f@sirjofri.de>

Quoth sirjofri <sirjofri+ml-9front@sirjofri.de>:
> Hello, reporting back!
> (Irc is fine, but people can't follow that easily, so here are my 
> results:)
> I installed cygwin and everything gcc that made sense, including the gcc 
> package and mingw-gcc. I didn't install any 32bit compilers as far as I 
> can tell. The installation target was my work windows 11 PC.
> Using CONF=win64 compiled without any issues. It used 
> x86_64-w64-mingw32-gcc for compiling. I verified the binary is 64-bit, 
> and not 32-bit. Starting works fine like I'd expect from a drawterm 
> application. No issues at runtime so far.
> 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.
> In the end, mingw works fine and is also what the Readme states. I 
> suggest adjusting the comment in the Make.win64 to prevent confusion and 
> then publish it.
> P.S. nice to have some 64-bit drawterm. I'd love to have it as a download 
> at drawterm.9front.org.
> sirjofri

pushed, thanks!

  reply	other threads:[~2022-05-15 15:48 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 [this message]
2022-05-15 15:57           ` sirjofri
2022-05-15 20:56           ` Amavect

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=07C1BD919339382B9EEC14724F2C8367@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \


* 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).