all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: Can't build previous versions of Emacs?
Date: Thu, 14 Jul 2022 09:13:26 -0700	[thread overview]
Message-ID: <8735f3d655.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87ilo0s70s.fsf@yahoo.com

Po Lu <luangruo@yahoo.com> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Hi all,
>>
>> I have the Emacs 25, 26 and 27 branches checked out in git worktrees,
>> and I was going to build them to test some backwards compatibility. On a
>> clean checkout, "make" failed for all three of them with this error:
>>
>> sysdep.c:1795:22: error: variably modified ‘sigsegv_stack’ at file scope
>>  1795 | static unsigned char sigsegv_stack[SIGSTKSZ];
>>       |                      ^~~~~~~~~~~~~
>> make[2]: *** [Makefile:377: sysdep.o] Error 1
>> make[2]: Leaving directory '/home/eric/dev/emacs-26/src'
>> make[1]: *** [Makefile:421: src] Error 2
>> make[1]: Leaving directory '/home/eric/dev/emacs-26'
>> make: *** [Makefile:1107: bootstrap] Error 2
>>
>> This is on Arch Linux, I can send the config.status file for any of the
>> branches if that would help.
>
> That's expected.  glibc recently changed in that SIGSTKSZ is now a call
> to a function.  Emacs wasn't modified to be compatible with that until
> 28.1.

Thanks! That's good to know.




  reply	other threads:[~2022-07-14 16:13 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  3:23 Can't build previous versions of Emacs? Eric Abrahamsen
2022-07-14  3:33 ` Po Lu
2022-07-14 16:13   ` Eric Abrahamsen [this message]
2022-07-14 17:07     ` Ulrich Mueller
2022-07-14 17:24       ` Lars Ingebrigtsen
2022-07-14 18:21         ` Stefan Monnier
2022-07-14 18:23           ` Lars Ingebrigtsen
2022-07-14 18:38             ` Stefan Monnier
2022-07-14 18:41               ` Lars Ingebrigtsen
2022-07-14 19:33                 ` Andreas Schwab
2022-07-14 21:52                 ` Stefan Kangas
2022-07-15  9:47                   ` Lars Ingebrigtsen
2022-07-15 13:37                     ` Stefan Kangas
2022-07-16 10:31                       ` Lars Ingebrigtsen
2022-07-16 11:03                         ` Po Lu
2022-07-16 11:05                           ` Lars Ingebrigtsen
2022-07-16 11:17                           ` Ulrich Mueller
2022-07-16 12:49                             ` Po Lu
2022-07-16 13:01                               ` Lars Ingebrigtsen
2022-07-16 14:54                                 ` Ulrich Mueller
2022-07-16 16:10                                   ` Lars Ingebrigtsen
2022-07-14 23:30           ` T.V Raman
2022-07-15 14:03             ` andrés ramírez
2022-07-15 14:50               ` Stefan Kangas
2022-07-15 15:30                 ` Eli Zaretskii
2022-07-16 20:59             ` Karl Berry
2022-07-17  0:49               ` Po Lu
2022-07-17  5:35                 ` Eli Zaretskii
2022-07-17  8:04                   ` Gregory Heytings
2022-07-17  8:53                     ` Po Lu
2022-07-17  8:56                       ` Gregory Heytings
2022-07-17  9:27                         ` Po Lu
     [not found]                   ` <DM6PR03MB3803454A10E226097F5A3877A68D9@DM6PR03MB3803.namprd03.prod.outlook.com>
     [not found]                     ` <83wncbq2ya.fsf@gnu.org>
2022-07-17 15:44                       ` andrés ramírez
2022-07-14 19:02       ` Alan Mackenzie
2022-07-14 17:01   ` Lars Ingebrigtsen

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=8735f3d655.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=emacs-devel@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.