From: Pierre Langlois <pierre.langlois@gmx.com>
To: 40556@debbugs.gnu.org
Cc: Julien Lepiller <julien@lepiller.eu>
Subject: [bug#40556] [PATCH] gnu: dovecot: Add libunwind input.
Date: Sat, 11 Apr 2020 17:42:50 +0200 [thread overview]
Message-ID: <87ftdahvut.fsf@gmx.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
Hi Guix, Julien,
I noticed I couldn't build dovecot on either aarch64 or arm :-/. I did a
little bit of debugging, and it looks like the backtrace_symbols()
function isn't working correctly. Dovecot is able to use libunwind
instead, and this appears to work.
I then noticed it was reported upstream already, coming to the same
conclusion https://markmail.org/message/fjgo7lkuk7tk4iek
I wonder what's wrong with backtrace_symbols() in guix, I'm not sure how
to investigate that. For now though, what do you think of using
libunwind?
Thanks,
Pierre
[-- Attachment #2: 0001-gnu-dovecot-Add-libunwind-input.patch --]
[-- Type: text/x-patch, Size: 1687 bytes --]
From b95b8f4769f5543d196fe7e334a891f8fe276816 Mon Sep 17 00:00:00 2001
From: Pierre Langlois <pierre.langlois@gmx.com>
Date: Sat, 11 Apr 2020 16:34:01 +0100
Subject: [PATCH] gnu: dovecot: Add libunwind input.
* gnu/packages/mail.scm (dovecot)[inputs]: Add libunwind.
---
gnu/packages/mail.scm | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/mail.scm b/gnu/packages/mail.scm
index a6ed776db1..4ea8fb6051 100644
--- a/gnu/packages/mail.scm
+++ b/gnu/packages/mail.scm
@@ -24,7 +24,7 @@
;;; Copyright © 2017 Kyle Meyer <kyle@kyleam.com>
;;; Copyright © 2017, 2018, 2019, 2020 Tobias Geerinckx-Rice <me@tobias.gr>
;;; Copyright © 2017, 2018 Rene Saavedra <pacoon@protonmail.com>
-;;; Copyright © 2018, 2019 Pierre Langlois <pierre.langlois@gmx.com>
+;;; Copyright © 2018, 2019, 2020 Pierre Langlois <pierre.langlois@gmx.com>
;;; Copyright © 2018 Alex Vong <alexvong1995@gmail.com>
;;; Copyright © 2018 Gábor Boskovits <boskovits@gmail.com>
;;; Copyright © 2018, 2019, 2020 Ricardo Wurmus <rekado@elephly.net>
@@ -89,6 +89,7 @@
#:use-module (gnu packages libevent)
#:use-module (gnu packages libidn)
#:use-module (gnu packages libunistring)
+ #:use-module (gnu packages libunwind)
#:use-module (gnu packages linux)
#:use-module (gnu packages lsof)
#:use-module (gnu packages lua)
@@ -1435,6 +1436,7 @@ facilities for checking incoming mail.")
(inputs
`(("bzip2" ,bzip2)
("libsodium" ,libsodium) ; extra password algorithms
+ ("libunwind" ,libunwind)
("linux-pam" ,linux-pam)
("lz4" ,lz4)
("openssl" ,openssl)
--
2.26.0
next reply other threads:[~2020-04-11 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 15:42 Pierre Langlois [this message]
2020-04-11 16:17 ` [bug#40556] [PATCH] gnu: dovecot: Add libunwind input Tobias Geerinckx-Rice via Guix-patches via
2020-04-11 16:53 ` Pierre Langlois
2020-04-11 17:56 ` Julien Lepiller
2020-04-16 16:24 ` Ludovic Courtès
2020-04-16 17:13 ` Pierre Langlois
2020-04-16 17:41 ` Pierre Langlois
2020-04-17 8:20 ` bug#40556: " Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftdahvut.fsf@gmx.com \
--to=pierre.langlois@gmx.com \
--cc=40556@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).