Why remove the AOT
configuration in the recent commits? It seems that we still need this option (NATIVE_FULL_AOT
) to compile the lisp code to native code.
Reference: https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/Makefile.in?h=master#n35
Git Clone URL: | https://aur.archlinux.org/emacs-git.git (read-only, click to copy) |
---|---|
Package Base: | emacs-git |
Description: | GNU Emacs. Development master branch. |
Upstream URL: | http://www.gnu.org/software/emacs/ |
Keywords: | development editor IDE text |
Licenses: | GPL3 |
Conflicts: | emacs |
Provides: | emacs |
Submitter: | toropisco |
Maintainer: | toropisco |
Last Packager: | toropisco |
Votes: | 104 |
Popularity: | 0.001815 |
First Submitted: | 2014-01-05 02:05 (UTC) |
Last Updated: | 2023-10-14 18:36 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 38 Next › Last »
Why remove the AOT
configuration in the recent commits? It seems that we still need this option (NATIVE_FULL_AOT
) to compile the lisp code to native code.
Reference: https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/Makefile.in?h=master#n35
All pkgbuild can be corrected, ffmpeg variants are usually correct and there are many, can't see why can't do the same
This pkgbuild (and all the emacs variants) only need to provides and conflicts emacs, not provide, conflicts and replace every variant
Exactly. Your statement applies to a perfect world but I don't work with ideal monads.
This pkgbuild (and all the emacs variants) only need to provides and conflicts emacs, not provide, conflicts and replace every variant
Thaodan, why do you think you have the right answer?
Why is gsettings disabled in any case? It only requires glib and doesn't have any gnome dependency necessarily. GSettings is supposed to replace XRessources for pgtk.
I've added a temporary fix to the PKGBUILD but it royally screws those who, like myself, do not like having the editor font depend on a desktop global setting. At least it works, for now.
It looks like they are addressing this problem upstream now:
https://lists.gnu.org/archive/html/emacs-devel/2022-05/msg00713.html
Apologies for the noise of reporting it here -- this appears to be an upstream problem, not a packaging problem.
@Rogach thanks, you're right -- I accidentally copy-pasted the most recent commit in my log instead of 526e9758, which was the most recent one to touch xsettings.c.
Pinned Comments
toropisco commented on 2017-06-30 19:14 (UTC) (edited on 2022-05-15 13:26 (UTC) by toropisco)
This PKGBUILD is a work in progress. If you find PACKAGING bugs, please let me know ASAP.
Upstream bugs are to be reported upstream. Check out the emacs-devel archives to confirm if this is an already known bug. In fact... Why are you not subscribed to
emacs-devel
?. Also check theemacs-bug-tracker
archives.Reporting bugs: Write to the Emacs Bug Tracker and report it there. Or, better yet, use the
debbugs
client included with the text editor. You will find instructions at https://debbugs.gnu.org/. Good luck!If you confirm it is a packaging bug, you are welcome to report it here.
Yaourt and other automated tools users BEWARE! This PKGBUILD is written with hand updating in mind and I won't fix bugs arising from such use. Besides, cloning the same repository time and time again from a non-profit such as the GNU Project/FSF gives out a very low image of you.