unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Akib Azmain Turja via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 66227@debbugs.gnu.org
Subject: bug#66227: 'emacs-next' is almost unusable
Date: Tue, 26 Sep 2023 19:49:50 +0600	[thread overview]
Message-ID: <87lectf3i9.fsf@disroot.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]


'emacs-next' doesn't work.  Because native-compilation doesn't work and
it breaks everything else.  Applying the following patch on Emacs 30
source should fix the problem.  (The patch for Emacs 29 won't work.)

--8<---------------cut here---------------start------------->8---
--- a/lisp/emacs-lisp/comp.el
+++ b/lisp/emacs-lisp/comp.el
@@ -203,9 +203,7 @@ and above."
   :type '(repeat string)
   :version "28.1")
 
-(defcustom native-comp-driver-options
-  (cond ((eq system-type 'darwin) '("-Wl,-w"))
-        ((eq system-type 'cygwin) '("-Wl,-dynamicbase")))
+(defcustom native-comp-driver-options nil
   "Options passed verbatim to the native compiler's back-end driver.
 Note that not all options are meaningful; typically only the options
 affecting the assembler and linker are likely to be useful.
-- 
2.38.0
--8<---------------cut here---------------end--------------->8---

-- 
Akib Azmain Turja, GPG key: 70018CE5819F17A3BBA666AFE74F0EFA922AE7F5
Fediverse: akib@hostux.social
Codeberg: akib
emailselfdefense.fsf.org | "Nothing can be secure without encryption."

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

             reply	other threads:[~2023-09-27 13:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 13:49 Akib Azmain Turja via Bug reports for GNU Guix [this message]
2023-10-06 14:39 ` bug#66227: 'emacs-next' is almost unusable Ricardo Wurmus
2023-10-06 15:58 ` bug#66227: [PATCH v3] gnu: emacs-next-minimal: Apply Guix patches Liliana Marie Prikler

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87lectf3i9.fsf@disroot.org \
    --to=bug-guix@gnu.org \
    --cc=66227@debbugs.gnu.org \
    --cc=akib@disroot.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).