unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: birdsite@airmail.cc
Cc: 50058@debbugs.gnu.org
Subject: bug#50058: 28.0.5; emacs build fails with undefined reference to malloc_info
Date: Sat, 14 Aug 2021 19:40:17 +0300	[thread overview]
Message-ID: <83zgtk9dzi.fsf@gnu.org> (raw)
In-Reply-To: <85lf5416vb.fsf@laptop.i-did-not-set--mail-host-address--so-tickle-me> (birdsite@airmail.cc)

> From: birdsite@airmail.cc
> Date: Sat, 14 Aug 2021 19:26:12 +0545
> 
> Recently while building emacs from source in void-linux using musl libc,
> the make program exits saying undefined reference to malloc_info.
> 
> Using git-bisect, i've found that the problem started with commit
> 621bb79b7044dcc277386eb7338c0eb1e08c29c7 `New debugging command
> 'malloc-info''
> This commit was introduced in 2020 Nov 10
> 
> The problem is present in the HEAD as of 2021 Aug 11 with commit
> 244acc5a057b0d6ff03754af14d71808b6f20233 `Replace some `string-match-p'
> calls in Tramp'
> 
> I beleive the problem exists because i'm using musl libc and not glibc.

Does musl define some preprocessor macro that we could use to
condition that function's compilation?





  reply	other threads:[~2021-08-14 16:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-14 13:41 bug#50058: 28.0.5; emacs build fails with undefined reference to malloc_info birdsite
2021-08-14 16:40 ` Eli Zaretskii [this message]
2021-08-14 17:08   ` Bird
2021-08-14 17:12   ` Lars Ingebrigtsen
2021-08-14 17:31     ` Eli Zaretskii
2021-08-14 17:39       ` Lars Ingebrigtsen
2021-08-15  1:59         ` Flappy Bird
2021-08-15 11:27           ` Lars Ingebrigtsen
2021-08-15 12:43             ` birdsite
2021-08-15 12:49               ` Lars Ingebrigtsen
2021-08-15 14:08                 ` birdsite
2021-08-15 14:20                   ` Lars Ingebrigtsen
2021-08-15 14:20               ` Eli Zaretskii

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zgtk9dzi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50058@debbugs.gnu.org \
    --cc=birdsite@airmail.cc \
    /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/emacs.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).