all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Andrea Corallo <acorallo@gnu.org>
Cc: 71916@debbugs.gnu.org, leuven65 <leuven65@gmail.com>
Subject: bug#71916: 31.0.50; build failure on MINGW64
Date: Wed, 03 Jul 2024 22:11:05 +0800	[thread overview]
Message-ID: <87plru4lc6.fsf@yahoo.com> (raw)
In-Reply-To: <yp1msmyk2fy.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Wed, 03 Jul 2024 09:52:33 -0400")

Andrea Corallo <acorallo@gnu.org> writes:

> leuven65 <leuven65@gmail.com> writes:
>
>> I found the latest version of both master and emacs-30 branch (from Monday) failed to be built on MINGW64 / windows10.
>> It failed when starting native compilation, error pops up "Cannot find libgccjit library" (from
>> comp-ensure-native-compiler), maybe the called function "load_gccjit_if_necessary / init_gccjit_functions" return error.
>>
>> But if to revert the change introduced by branch "savannah/scratch/windows-98" (merged on 2024/06/30), the build becomes
>> OK.
>>
>>  git revert 38179f85f8f7236d5de8d9a4333b6a1d4ded63f0
>>
>> So that maybe the issue is caused by the 3 commits in this branch.
>
> Hello leuven65,
>
> could you share the exact error you observe?
>
> Ccing Po Lo
>
> Thanks
>
>   Andrea

Yes, please, thanks.





  reply	other threads:[~2024-07-03 14:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03 13:43 bug#71916: 31.0.50; build failure on MINGW64 leuven65
2024-07-03 13:52 ` Andrea Corallo
2024-07-03 14:11   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-07-03 16:24   ` leuven65
2024-07-03 18:02   ` Andy Moreton
2024-07-03 19:15     ` Eli Zaretskii
2024-07-03 21:47       ` Andy Moreton
2024-07-03 22:09         ` Andrea Corallo

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=87plru4lc6.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=71916@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=leuven65@gmail.com \
    --cc=luangruo@yahoo.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.