emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#40556: closed ([PATCH] gnu: dovecot: Add libunwind input.)


From: GNU bug Tracking System
Subject: bug#40556: closed ([PATCH] gnu: dovecot: Add libunwind input.)
Date: Fri, 17 Apr 2020 08:21:02 +0000

Your message dated Fri, 17 Apr 2020 10:20:34 +0200
with message-id <address@hidden>
and subject line Re: [bug#40556] [PATCH] gnu: dovecot: Add libunwind input.
has caused the debbugs.gnu.org bug report #40556,
regarding [PATCH] gnu: dovecot: Add libunwind input.
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
40556: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=40556
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: [PATCH] gnu: dovecot: Add libunwind input. Date: Sat, 11 Apr 2020 17:42:50 +0200 User-agent: mu4e 1.2.0; emacs 26.3
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: 0001-gnu-dovecot-Add-libunwind-input.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: [bug#40556] [PATCH] gnu: dovecot: Add libunwind input. Date: Fri, 17 Apr 2020 10:20:34 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
Hi Pierre,

Pierre Langlois <address@hidden> skribis:

> Right, it seems dovecot isn't yet cross-compilable, but cross-compiling
> libunwind works just fine. With dovecot I get a failure trying to
> compile perl natively, as openssl's native-input I believe.

Not your fault, and it’s fixed on core-updates as you write.

I’ve applied the patch, thank you!

Ludo’.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]