all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mark A. Hershberger" <mah@nichework.com>
Cc: mah@everybody.org, 61125@debbugs.gnu.org, akrl@sdf.org
Subject: bug#61125: 30.0.50; debug build fails
Date: Sun, 29 Jan 2023 09:31:55 +0200	[thread overview]
Message-ID: <837cx594pg.fsf@gnu.org> (raw)
In-Reply-To: <1227832933.27615.1674939535166.JavaMail.zimbra@nichework.com> (mah@nichework.com)

> Date: Sat, 28 Jan 2023 12:58:55 -0800 (PST)
> From: "Mark A. Hershberger" <mah@nichework.com>
> Cc: "Mark A. Hershberger" <mah@everybody.org>, Andrea Corallo <akrl@sdf.org>, 
> 	61125@debbugs.gnu.org
> 
> Relevant bits from my script are below.
> 
> buildIt() {
> 	banner buildIt
> 	FLAGS=$1
> 
> 	./autogen.sh
> 	./configure						\
> 		--with-gif=ifavailable				\
> 		--with-tree-sitter=ifavailable			\
> 		--with-cairo					\
> 		--with-imagemagick				\
> 		--with-json					\
> 		--with-native-compilation			\
> 		--with-xinput2					\
> 		--with-xwidgets					\
> 		--with-x-toolkit=gtk3				\
> 		--with-gconf					\
> 		--with-xwidgets					\
> 		--with-imagemagick				\
> 		--with-modules					\
> 		$FLAGS
> 	make -j6
> }
> 
> flags="--enable-checking=yes,glyphs --enable-check-lisp-object-type"
> CFLAGS="-O0 -g3" buildIt "$flags"

I enlarged F_RELOC_MAX_SIZE, please see if the problem is solved.





  reply	other threads:[~2023-01-29  7:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 18:18 bug#61125: 30.0.50; debug build fails Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-28 20:15 ` Eli Zaretskii
2023-01-28 20:58   ` Mark A. Hershberger
2023-01-29  7:31     ` Eli Zaretskii [this message]
2023-01-30  5:08       ` Mark A. Hershberger
2023-01-30 12:52         ` 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

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

  git send-email \
    --in-reply-to=837cx594pg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61125@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=mah@everybody.org \
    --cc=mah@nichework.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 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.