From: Andy Moreton <andrewjmoreton@gmail.com>
To: cygwin@cygwin.com
Subject: Re: libgccjit
Date: Sun, 14 Mar 2021 19:06:01 +0000 [thread overview]
Message-ID: <86h7ldpnc6.fsf@gmail.com> (raw)
In-Reply-To: <87pn01n1p2.fsf@Rainer.invalid>
On Sun 14 Mar 2021, Achim Gratz wrote:
> Jonathan Yong via Cygwin writes:
>> Thanks for trying.
>> Does injecting dlfcn.h work?
>
> The include is not used because it is tied to --enable-plugins. Plugins
> do not work because the configury determines that shared objects do not
> work. If I manually force the inclusion some other stuff goes missing
> apparently, but let me try to re-start the build from the beginning with
> the patch already applied… well, it stops at the same problem again:
>
> make[3]: *** No rule to make target 'xgcc', needed by 'x86_64-pc-cygwin-gcc-10.exe'. Stop.
>
> But really, the first steps would apparently be to make --enable-plugins
> do something sane on Cygwin (there seems to have been work on this for
> MingW64, but it doesn't look like there are patches anywhere I can
> find).
The build scripts for Mingw64 in the MSYS2 distro are here:
https://github.com/msys2/MINGW-packages/tree/master/mingw-w64-gcc
The PKGBUILD file is the build script (same tooling as Arch linux), and
the local patches there may help guide similar fixes for Cygwin.
AndyM
next prev parent reply other threads:[~2021-03-14 19:06 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 ` Andy Moreton [this message]
2021-03-14 20:22 ` libgccjit Achim Gratz
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=86h7ldpnc6.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--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).