all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, 52711@debbugs.gnu.org
Subject: bug#52711: undefined reference to '__muloti4'
Date: Tue, 21 Dec 2021 20:12:07 +0000	[thread overview]
Message-ID: <YcI1F2M9wD0GRORp@idiocy.org> (raw)
In-Reply-To: <83y24dyc2i.fsf@gnu.org>

On Tue, Dec 21, 2021 at 09:47:49PM +0200, Eli Zaretskii wrote:
> > Date: Tue, 21 Dec 2021 19:30:42 +0000
> > From: Alan Third <alan@idiocy.org>
> > 
> > I no longer seem to be able to build the master branch. I'm getting
> > this error:
> > 
> >   CCLD     temacs
> > fileio.c:6261: error: undefined reference to '__muloti4'
> > clang: error: linker command failed with exit code 1 (use -v to see invocation)
> > make[2]: *** [Makefile:697: temacs] Error 1
> > 
> > I had a look but couldn't see where the problem comes from. I'm using
> > clang on Debian testing, if that matters.
> 
> Try using "nm -A fileio.o" to see what is that function and which code
> calls it.
> 
> If nothing else helps, try bisecting.  (But my crystal ball says it
> isn't Emacs that changed, it's something else on that system.)

Looks like it's gnulib:

f05a93e8232e6f56458ac16d733b03e96a63e930 is the first bad commit
commit f05a93e8232e6f56458ac16d733b03e96a63e930
Author: Paul Eggert <eggert@cs.ucla.edu>
Date:   Sat Dec 18 16:12:38 2021 -0800
    Update from gnulib

I think the actual call is deep within some nested macros.
-- 
Alan Third





  reply	other threads:[~2021-12-21 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 19:30 bug#52711: undefined reference to '__muloti4' Alan Third
2021-12-21 19:47 ` Eli Zaretskii
2021-12-21 20:12   ` Alan Third [this message]
2021-12-21 20:17     ` Eli Zaretskii
2021-12-21 21:26       ` Alan Third
2021-12-21 23:41     ` Paul Eggert
2021-12-22 13:53       ` Alan Third

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

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

  git send-email \
    --in-reply-to=YcI1F2M9wD0GRORp@idiocy.org \
    --to=alan@idiocy.org \
    --cc=52711@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.