all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "F. Romage" <mrfromage@comcast.net>
Cc: 62895@debbugs.gnu.org
Subject: bug#62895: Emacs 28.2 NS build segfaults on startup
Date: Thu, 20 Apr 2023 11:13:08 +0800	[thread overview]
Message-ID: <87edoffdq3.fsf@yahoo.com> (raw)
In-Reply-To: <1607403012.445352.1681957120092@connect.xfinity.com> (F. Romage's message of "Wed, 19 Apr 2023 22:18:40 -0400 (EDT)")

"F. Romage" <mrfromage@comcast.net> writes:

>> On 04/18/2023 10:38 PM Po Lu <luangruo@yahoo.com> wrote:
>> The GNUstep build works in Emacs 29.  Large parts of its font driver
>> have also been rewritten, so text display problems should no longer be present.
>
> Today I checked out the latest code using git, which gave me this version information:
>
> GNU Emacs 30.0.50
> Development version a01528c95002 on master branch; build date 2023-04-19.
>
> I was able to build using --with-ns but got the same segfault when running it as I did with 28.2. Was there a regression from Emacs 29 to 30 for the NS build?

Then would you please show a backtrace from the crash, and also tell
which version of GNUstep you have installed?  It works for me.





  reply	other threads:[~2023-04-20  3:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 21:54 bug#62895: Emacs 28.2 NS build segfaults on startup F. Romage
2023-04-19  2:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-20  2:18   ` F. Romage
2023-04-20  3:13     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-04-23 18:52       ` F. Romage
2023-04-24  0:47         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87edoffdq3.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=62895@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=mrfromage@comcast.net \
    /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.