From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#50058: 28.0.5; emacs build fails with undefined reference to malloc_info Date: Sat, 14 Aug 2021 20:31:23 +0300 Message-ID: <83y2949bmc.fsf@gnu.org> References: <85lf5416vb.fsf@laptop.i-did-not-set--mail-host-address--so-tickle-me> <83zgtk9dzi.fsf@gnu.org> <87pmugq7ay.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30521"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 50058@debbugs.gnu.org, birdsite@airmail.cc To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Aug 14 19:33:11 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mExWw-0007kf-W0 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 14 Aug 2021 19:33:10 +0200 Original-Received: from localhost ([::1]:41034 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mExWu-0001AB-N4 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 14 Aug 2021 13:33:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43138) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mExWp-00019p-7L for bug-gnu-emacs@gnu.org; Sat, 14 Aug 2021 13:33:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:33798) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mExWp-0000Uo-0e for bug-gnu-emacs@gnu.org; Sat, 14 Aug 2021 13:33:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mExWn-00084E-OM for bug-gnu-emacs@gnu.org; Sat, 14 Aug 2021 13:33:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 14 Aug 2021 17:33:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 50058 X-GNU-PR-Package: emacs Original-Received: via spool by 50058-submit@debbugs.gnu.org id=B50058.162896233330916 (code B ref 50058); Sat, 14 Aug 2021 17:33:01 +0000 Original-Received: (at 50058) by debbugs.gnu.org; 14 Aug 2021 17:32:13 +0000 Original-Received: from localhost ([127.0.0.1]:45344 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mExVx-00082T-EM for submit@debbugs.gnu.org; Sat, 14 Aug 2021 13:32:13 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:54810) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mExVp-00081m-GS for 50058@debbugs.gnu.org; Sat, 14 Aug 2021 13:32:08 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55384) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mExVj-00087a-Mi; Sat, 14 Aug 2021 13:31:55 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1270 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mExVe-0004ME-Mv; Sat, 14 Aug 2021 13:31:54 -0400 In-Reply-To: <87pmugq7ay.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 14 Aug 2021 19:12:37 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:211852 Archived-At: > From: Lars Ingebrigtsen > Cc: birdsite@airmail.cc, 50058@debbugs.gnu.org > Date: Sat, 14 Aug 2021 19:12:37 +0200 > > I think musl, on purpose, doesn't define anything to allow us to > identify that we're using it? > > https://wiki.musl-libc.org/faq.html > > Or I may be misunderstanding something. > > But if that's the case, we have to just test explicitly for malloc_info > in configure.ac... Yes. Or we could use something to single out glibc, if there is such a macro.