From: Thomas Klausner <tk@giga.or.at>
To: 25921@debbugs.gnu.org
Cc: Greg Troxel <gdt@lexort.com>
Subject: bug#25921: pkgsrc patches: Dragonfly support
Date: Wed, 1 Mar 2017 21:27:10 +0100 [thread overview]
Message-ID: <20170301202710.t3wqopzxihnoo3hq@danbala> (raw)
[-- Attachment #1: Type: text/plain, Size: 207 bytes --]
Hi!
We have a couple of patches in pkgsrc for guile which I'd like to see
merged.
The attached ones are for supporting DragonFly
(https://www.dragonflybsd.org/) better.
Can you please merge them?
Thomas
[-- Attachment #2: patch-lib_signal.in.h --]
[-- Type: text/plain, Size: 507 bytes --]
$NetBSD: patch-lib_signal.in.h,v 1.1 2016/12/03 03:15:33 marino Exp $
DragonFly support.
--- lib/signal.in.h.orig 2016-06-29 09:12:27 UTC
+++ lib/signal.in.h
@@ -61,6 +61,7 @@
#if (@GNULIB_PTHREAD_SIGMASK@ || defined GNULIB_POSIXCHECK) \
&& ((defined __APPLE__ && defined __MACH__) \
|| defined __FreeBSD__ || defined __OpenBSD__ || defined __osf__ \
+ || defined __DragonFly__ \
|| defined __sun || defined __ANDROID__) \
&& ! defined __GLIBC__
# include <pthread.h>
[-- Attachment #3: patch-libguile_threads.c --]
[-- Type: text/plain, Size: 449 bytes --]
$NetBSD: patch-libguile_threads.c,v 1.1 2016/12/03 03:15:33 marino Exp $
DragonFly support.
--- libguile/threads.c.orig 2016-06-20 20:35:06 UTC
+++ libguile/threads.c
@@ -2252,7 +2252,7 @@ scm_ia64_ar_bsp (const void *opaque)
return (void *) ctx->uc_mcontext.sc_ar_bsp;
}
# endif /* linux */
-# ifdef __FreeBSD__
+# if defined __FreeBSD__ || defined __DragonFly__
# include <ucontext.h>
void *
scm_ia64_register_backing_store_base (void)
next reply other threads:[~2017-03-01 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 20:27 Thomas Klausner [this message]
2017-03-14 11:27 ` bug#25921: pkgsrc patches: Dragonfly support Andy Wingo
2017-03-15 18:04 ` Thomas Klausner
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170301202710.t3wqopzxihnoo3hq@danbala \
--to=tk@giga.or.at \
--cc=25921@debbugs.gnu.org \
--cc=gdt@lexort.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).