Package Details: emacs-gcc-wayland-devel-bin

Git Clone URL: (read-only, click to copy)
Package Base: emacs-gcc-wayland-devel-bin
Description: GNU Emacs. Development native-comp branch and pgtk branch combined, served as a binary.
Upstream URL:
Keywords: emacs
Licenses: GPL3
Conflicts: emacs, emacs-27-git, emacs-git, emacs-seq, emacs26-git
Provides: emacs, emacs-seq
Replaces: emacs-git, emacs-seq, emacs26-git, emacs27-git
Submitter: mpsq
Maintainer: mpsq
Last Packager: mpsq
Votes: 10
Popularity: 5.08
First Submitted: 2020-12-03 15:47
Last Updated: 2021-03-05 15:20

Required by (413)

Sources (1)

Latest Comments

mpsq commented on 2021-03-02 18:26

Hey guys, Emacs upstream was updated recently (compilation flags) and I just reflected the changes in this binary. If you had issues with doom-emacs (doom upgrade), or native-comp in general, this is now fixed.

jeslie0 commented on 2021-02-12 18:13

@mpsq I think I am having strange upscaling issues from using a 4k monitor. There is an open issue thread about it here:

mpsq commented on 2021-02-12 15:48

@jeslie0 This is very stange, I open svg files on a daily basis and never had this issue. Is there anything special with your Emacs setup? Does it happen for all svgs? Are you zoomed-in?

jeslie0 commented on 2021-02-07 20:18

I'm having an issue where .svg files are blurry when viewed from inside Emacs (using "emacs -Q" also). It looks like an instance of the bug described here:

Is this a known bug or is it affecting anyone else?

langtudeplao commented on 2020-12-23 09:35

Thank you for maintaining this packages. I installed emacs fresh from this package to solve the blurry problem with xwayland. So far, everything works perfectly.

bienjensu commented on 2020-12-22 14:50

@mpsq I can confirm that rolling back to 6d6b07b793f2c7d993fe238f99a63c4644dd44ed fixed the problem. Thanks for the help!

mpsq commented on 2020-12-22 14:32

@bienjensu Fair enough, I tried and I can reproduce the issue.

I checked and this is a problem with Emacs itself, if you try the last version (of this pkg) everything is ok. The regression is from upstream and there is not much I can do to fix it. You should be able to roll-back to the last version though.

I might add additional checks in my building script, make sure that Emacs starts without warnings/errors before pushing a new version.

bienjensu commented on 2020-12-22 14:07

@mpsq Hello, yes I'm running without any config at all right now in order to diagnose problems.

mpsq commented on 2020-12-22 13:56

Hi Edward, I am not sure what the issue is from the top of my head. Maybe we can "work backwards": did you try to run vanilla Emacs? (without your personal config)

The error you are facing seems to be related to Are you using this as part of your Emacs config by any chance?

bienjensu commented on 2020-12-22 13:31

Hi, I'm getting errors with this. Everything is left at default in the PKGBUILD, my pkgmake.conf only changes -j and march=native on MAKEFLAGS. These errors repeat every time that after emacs is launched something starts native compilation (following the startpage link to the tutorial, for instance). *Warnings*:

Warning (comp): Debugger entered--Lisp error: (file-error "Opening output file" "Cannot overwrite file" "/usr/share/emacs/28.0.50/lisp/emacs-lisp/cl-lib.el...") Disable showing Disable logging


Debugger entered--Lisp error: (file-error "Opening output file" "Cannot overwrite file" "/usr/share/emacs/28.0.50/lisp/emacs-lisp/cl-lib.el...")
signal(file-error ("Opening output file" "Cannot overwrite file" "/usr/share/emacs/28.0.50/lisp/emacs-lisp/cl-lib.el..."))
#f(compiled-function (filename) "Byte-compile FILENAME spilling data from the byte compiler." #<bytecode 0x15639fb902450803>)("/usr/share/emacs/28.0.50/lisp/emacs-lisp/cl-lib.el")
apply(#f(compiled-function (filename) "Byte-compile FILENAME spilling data from the byte compiler." #<bytecode 0x15639fb902450803>) "/usr/share/emacs/28.0.50/lisp/emacs-lisp/cl-lib.el" nil)
#f(compiled-function (pass) #<bytecode 0x8df95ff29d600bb>)(comp-spill-lap)
mapc(#f(compiled-function (pass) #<bytecode 0x8df95ff29d600bb>) (comp-spill-lap comp-limplify comp-fwprop comp-call-optim comp-ipa-pure comp-cond-cstr comp-fwprop comp-dead-code comp-tco comp-fwprop comp-remove-type-hints comp-final))
comp--native-compile("/usr/share/emacs/28.0.50/lisp/emacs-lisp/cl-lib.el" t)
eval-buffer(#<buffer  *load*> nil "/tmp/emacs-async-comp-cl-lib-OWDUvK.el" nil t)  ; Reading at buffer position 1385
load-with-code-conversion("/tmp/emacs-async-comp-cl-lib-OWDUvK.el" "/tmp/emacs-async-comp-cl-lib-OWDUvK.el" nil t)
command-line-1(("-l" "/tmp/emacs-async-comp-cl-lib-OWDUvK.el"))

These repeat for all files emacs is attempting to native comp. I've already tried completely clearing out all configuration files, purging my /usr/lib/emacs and /usr/share/emacs, and reinstalling to no avail.