From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [Package Request] GccEmacs
Date: Sat, 24 Oct 2020 06:25:36 +0200 [thread overview]
Message-ID: <20201024042536.nuUSPGjkf8e4w1r6soEDFreMRw7O1G-7X4qSr3160wg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24240@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/24240#issuecomment-715671265
Comment:
@ap4y is this currently working on musl? I needed this patch:
```patch
Fix poisoned calloc errors when building libgccjit
---
gcc/jit/jit-playback.c | 4 ++--
gcc/jit/jit-recording.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/gcc/jit/jit-playback.c b/gcc/jit/jit-playback.c
index b74495c58..070463d71 100644
--- a/gcc/jit/jit-playback.c
+++ b/gcc/jit/jit-playback.c
@@ -18,6 +18,8 @@ You should have received a copy of the GNU General Public License
along with GCC; see the file COPYING3. If not see
<http://www.gnu.org/licenses/>. */
+#include <pthread.h>
+
#include "config.h"
#include "system.h"
#include "coretypes.h"
@@ -40,8 +42,6 @@ along with GCC; see the file COPYING3. If not see
#include "gcc.h"
#include "diagnostic.h"
-#include <pthread.h>
-
#include "jit-playback.h"
#include "jit-result.h"
#include "jit-builtins.h"
diff --git a/gcc/jit/jit-recording.c b/gcc/jit/jit-recording.c
index a332fe875..7184a481a 100644
--- a/gcc/jit/jit-recording.c
+++ b/gcc/jit/jit-recording.c
@@ -18,6 +18,8 @@ You should have received a copy of the GNU General Public License
along with GCC; see the file COPYING3. If not see
<http://www.gnu.org/licenses/>. */
+#include <pthread.h>
+
#include "config.h"
#include "system.h"
#include "coretypes.h"
@@ -25,8 +27,6 @@ along with GCC; see the file COPYING3. If not see
#include "pretty-print.h"
#include "toplev.h"
-#include <pthread.h>
-
#include "jit-builtins.h"
#include "jit-recording.h"
#include "jit-playback.h"
--
2.28.0
```
next prev parent reply other threads:[~2020-10-24 4:25 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 11:57 [ISSUE] [Package Request] GCCemacs zenny
2020-08-13 9:03 ` [Package Request] GccEmacs leahneukirchen
2020-08-13 12:10 ` zenny
2020-08-13 12:20 ` zenny
2020-08-16 23:31 ` Javyre
2020-08-17 7:45 ` zenny
2020-08-17 7:55 ` zenny
2020-08-21 0:27 ` Javyre
2020-09-27 23:10 ` ap4y
2020-10-24 4:25 ` ericonr [this message]
2020-10-29 8:49 ` zenny
2020-10-29 8:50 ` zenny
2020-10-29 19:36 ` zenny
2020-11-03 17:59 ` Javyre
2020-11-03 17:59 ` Javyre
2020-11-05 8:09 ` zenny
2020-11-05 14:45 ` Javyre
2020-11-05 21:00 ` zenny
2020-11-06 5:24 ` zenny
2020-11-06 18:33 ` zenny
2020-11-09 9:43 ` zenny
2020-11-09 9:43 ` [ISSUE] [CLOSED] " zenny
2021-02-15 21:06 ` lane-brain
2021-02-15 22:38 ` ericonr
2021-02-16 0:29 ` ericonr
2021-02-16 1:08 ` lane-brain
2021-02-16 1:10 ` lane-brain
2021-02-16 1:11 ` lane-brain
2021-02-16 1:12 ` lane-brain
2021-02-16 1:13 ` lane-brain
2021-02-16 1:14 ` lane-brain
2021-02-16 1:15 ` lane-brain
2021-02-16 1:19 ` ericonr
2021-02-16 1:40 ` lane-brain
2021-02-16 1:40 ` lane-brain
2021-02-27 0:12 ` xianwenchen
2021-06-22 18:20 ` lulcat
2021-06-22 18:21 ` lulcat
2021-10-17 8:03 ` basicfunc
2021-10-17 15:47 ` leahneukirchen
2022-01-11 10:01 ` soanvig
2022-01-11 14:07 ` basicfunc
2022-01-11 14:09 ` basicfunc
2022-04-16 14:05 ` [ISSUE] [CLOSED] " leahneukirchen
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=20201024042536.nuUSPGjkf8e4w1r6soEDFreMRw7O1G-7X4qSr3160wg@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).