public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: libgccjit
Date: Mon, 05 Apr 2021 21:01:10 +0200	[thread overview]
Message-ID: <87mtuctv2h.fsf@Rainer.invalid> (raw)
In-Reply-To: <87wnthu946.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 04 Apr 2021 21:45:29 +0200")

Achim Gratz writes:
> Other than that, I'll probably provide test packages for the 10.3.0-RC1
> since I have to get that going anyway.

Now that I have also built the 32bit version I see that the JIT tests
fail there because the JIT executables don't seem to invoke the linker
correctly and ld in turn doesn't find the necessary DLL and object files
to link to.  That may only be a problem for the test environment and go
away when the compiler is properly installed or it may be something
deeper in the build / configuration.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

      parent reply	other threads:[~2021-04-05 19:01 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               ` 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   ` Achim Gratz [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=87mtuctv2h.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).