Send MinGW-Notify mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.osdn.me/mailman/listinfo/mingw-notify
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of MinGW-Notify digest..."
Please do not reply to this notification; the sender address is unable to
accept incoming e-mail. If you wish to unsubscribe you can do so at
https://lists.osdn.me/mailman/listinfo/mingw-notify.
Today's Topics:
1. [mingw] #41070: Please include libgccjit with MinGW GCC
distribution (MinGW Notification List)
----------------------------------------------------------------------
Message: 1
Date: Mon, 11 Jan 2021 17:57:00 +0200
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #41070: Please include libgccjit with
MinGW GCC distribution
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8
#41070: Please include libgccjit with MinGW GCC distribution
Open Date: 2020-12-23 19:28
Last Update: 2021-01-11 17:56
URL for this Ticket:
https://osdn.net//projects/mingw/ticket/41070
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=41070
---------------------------------------------------------------------
Last Changes/Comment on this Ticket:
2021-01-11 17:56 Updated by: eliz
Comment:
Reply To keith
Reply To eliz
Reply To keith
Reply To eliz
I think statically linking against libintl is a Good Thing,
Are you saying that you have applications which depend on your
older release of libintl-8.dll, and which will not work with
MinGW's latest libintl-8.dll release?
No, that's not what I'm saying. I said "a bit of DLL hell" because I'll
have to cope with 2 different DLLs with the same name.
Why? You should need only the most recent release of libintl-8.dll,
(whether yours or mine), and all of your dependent applications should be
happy; no need for your own (older) version. Besides, if static linking is
such a "good thing", why don't you just link your own applications
statically? If you did this, why was your libintl-8.dll ever needed anyway?
Forgive me, but I simply don't understand your reasoning here.
I've seen libintl-8.dll versions that caused crashes on program exit, so I'm
trying to use only the ones I trust. Maybe the one we have now on the MinGW
site can also be trusted, but I will need to collect that experience from
scratch.
IOW, I simply value my extremely stable system, and would like it to remain
stable. So I try to avoid unnecessary changes to the basics, and libintl is
part of that.
I hope this explains my reasoning.
---------------------------------------------------------------------
Ticket Status:
Reporter: eliz
Owner: keith
Type: Feature Request
Status: Open [Owner assigned]
Priority: 5 - Medium
MileStone: (None)
Component: GCC
Severity: 5 - Medium
Resolution: None
---------------------------------------------------------------------
Ticket details:
Please add libgccjit to the binaries included in the MinGW GCC distributions.
This is required to be able to build projects that use libgccjit for JIT
compilation of code. One example of this is "gccemacs", a branch of GNU Emacs
development (soon to land on the master branch of Emacs) that compiles Emacs
Lisp programs into native x86 code for faster runtime performance.
Thank you.
--
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN
Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net
URL for this Ticket:
https://osdn.net/projects/mingw/ticket/41070
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=41070
------------------------------
Subject: Digest Footer
_______________________________________________
MinGW-Notify mailing list
[email protected]
https://lists.osdn.me/mailman/listinfo/mingw-notify
------------------------------
End of MinGW-Notify Digest, Vol 40, Issue 10
********************************************
