From: Julien Lepiller <julien@lepiller.eu>
To: Pierre Langlois <pierre.langlois@gmx.com>,
Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 40556@debbugs.gnu.org
Subject: [bug#40556] [PATCH] gnu: dovecot: Add libunwind input.
Date: Sat, 11 Apr 2020 13:56:42 -0400 [thread overview]
Message-ID: <5AA1CEE8-556B-48A9-BA51-86686EDD0482@lepiller.eu> (raw)
In-Reply-To: <87eesuhsl2.fsf@gmx.com>
Le 11 avril 2020 12:53:29 GMT-04:00, Pierre Langlois <pierre.langlois@gmx.com> a écrit :
>
>Tobias Geerinckx-Rice writes:
>
>> Pierre,
>>
>> Pierre Langlois 写道:
>>> 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?
>>
>> OK, but it should only be included on platforms that require it:
>
>Oh sure thing!
>
>>
>> ;; Untested…
>> (inputs
>> `(…
>> ,@(match (%current-system)
>> ((or "aarch64-linux" "armhf-linux" …)
>> `(("libunwind" ,libunwind)))
>> (_ `()))
>> …))
>>
>> Could you test that?
>
>OK, the following patch works for me (tested building for armhf and
>aarch64 on a rockpro64). I've also added a "FIXME" comment to mention
>the issue so we can remove/keep it when we have a good understanding of
>what's going on.
Great, thanks for working on it, I had totally forgotten about it, because I fixed it in my systems by not running tests. There's also a bug report I sent to bug-guix I think. Adding libunwind should work. I remember testing it once, but it was just too long and I forgot about it ^^"
next prev parent reply other threads:[~2020-04-11 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 15:42 [bug#40556] [PATCH] gnu: dovecot: Add libunwind input Pierre Langlois
2020-04-11 16:17 ` Tobias Geerinckx-Rice via Guix-patches via
2020-04-11 16:53 ` Pierre Langlois
2020-04-11 17:56 ` Julien Lepiller [this message]
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=5AA1CEE8-556B-48A9-BA51-86686EDD0482@lepiller.eu \
--to=julien@lepiller.eu \
--cc=40556@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=pierre.langlois@gmx.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 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).