From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: libgccjit
Date: Sun, 14 Mar 2021 21:22:54 +0100 [thread overview]
Message-ID: <87im5tmqn5.fsf@Rainer.invalid> (raw)
In-Reply-To: <86h7ldpnc6.fsf@gmail.com> (Andy Moreton via Cygwin's message of "Sun, 14 Mar 2021 19:06:01 +0000")
Andy Moreton via Cygwin writes:
> The build scripts for Mingw64 in the MSYS2 distro are here:
>
> https://github.com/msys2/MINGW-packages/tree/master/mingw-w64-gcc
Ah, OK. Thanks.
> The PKGBUILD file is the build script (same tooling as Arch linux), and
> the local patches there may help guide similar fixes for Cygwin.
It seems these take quite a different path than what I had in mind. But
there seems to be confirmation in there that one would not need plugins
or host-shared enabled for gccjit. Getting rid of host-shared makes the
build a lot closer to what it has been before I think and might then not
need as extensive a surgery to get the rest of the build into line.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2021-03-14 20:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 17:00 libgccjit Ken Brown
2021-03-11 10:16 ` libgccjit Corinna Vinschen
2021-03-11 16:00 ` libgccjit Jonathan Yong
2021-03-13 20:28 ` libgccjit Achim Gratz
2021-03-14 6:52 ` libgccjit Achim Gratz
2021-03-14 14:54 ` libgccjit Jonathan Yong
2021-03-14 16:24 ` libgccjit Achim Gratz
2021-03-14 19:06 ` libgccjit Andy Moreton
2021-03-14 20:22 ` Achim Gratz [this message]
2021-03-14 21:19 ` libgccjit Andy Moreton
2021-03-14 20:42 ` libgccjit Achim Gratz
2021-03-11 17:19 ` libgccjit Achim Gratz
2021-04-04 19:45 ` libgccjit Achim Gratz
2021-04-04 20:39 ` libgccjit Ken Brown
2021-04-05 19:01 ` libgccjit Achim Gratz
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=87im5tmqn5.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.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).