Hot answers tagged

20

Take a look at the system-configuration-options variable. Here's an example, which is the result of running C-h v system-configuration-options system-configuration-options is a variable defined in `C source code'. Its value is "--prefix=/usr/local/emacs 'CFLAGS=-O2 -march=native -pipe -falign-functions=64 -fomit-frame-pointer -ftracer -funit-at-a-time -...


12

There are a number of Emacs versions for macOS, including: The official Emacs on macOS is build using the "NS" port, also known as the "cocoa" port. As the name suggests, this port of Emacs originates in Emacs for the NextSTEP operating system and has been the official Emacs GUI on macOS since Emacs 23. Mitsuharu Yamamoto-san maintains the "Mac port" of ...


10

It is recommended that users read the entire ../emacs/nt/INSTALL contained within the Emacs source code. Quick Start -- 5 Easy Steps: This answer was tested on WindowsXP--SP3. The installation paths will need to be adjusted based on the individual preferences of the user. In this example: The desktop is: C:\Documents and Settings\lawlist\Desktop The ...


8

The reason 24.5 builds so quickly for you is that the .elc files are actually distributed in the tarball, see make-dist. When building from git, the majority of the time is spent compiling the .el files into .elc. By optimizing the C code, the Lisp compilation can go faster, but it still takes a long time. Compare build times using your original settings (...


6

In the release log of emacs:(http://www.gnu.org/software/emacs/news/NEWS.24.5) * Installation Changes in Emacs 24.3 ** The default X toolkit is now Gtk+ version 3. If you don't pass `--with-x-toolkit' to configure, or if you use `--with-x-toolkit=gtk' or `--with-x-toolkit=yes', configure will try to build with Gtk+ version 3, and if that fails, try Gtk+ ...


6

This question is also being answered here (since you already found my github bug report): https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23529 For the moment, and likely it will be this way until the emacs build system changes, the only valid solutions are: Don't build with a Dockerfile and build in a running container that has a seccomp profile that ...


6

The vast bulk of Emacs libraries are not included in the emacs executable; so if you never use them, they are merely taking up a little space on the filesystem. With modern hard disk sizes, I think it's extremely unlikely to be worth your time deleting any of them to reclaim space. The only elisp libraries which are directly included in the emacs executable ...


5

Found the solution: I was missing the package libdbus-1-dev. After ./configure && make dbus support was automatically added. So basically follow: sudo apt-get install libdbus-1-dev ./autogen.sh ./configure make


4

Any Emacs can show you how it was configured at build-time. Inspect the value of system-configuration-options with Meta+h v. A recent Emacs from https://emacsformacosx.com/ shows: system-configuration-options is a variable defined in ‘C source code’. Its value is "--with-ns '--enable-locallisppath=/Library/Application Support/Emacs/${version}/site-lisp:/...


3

TL;DR export PATH=/usr/bin:/bin I had a look at config.log to see where configure mentioned the paths used by the Anaconda distribution and I found 3 references to miniconda3 — 2 were related to the PNG libraries and one to the PATH variable... of course the bin directory of the Anaconda distribution has to be prepended to PATH, hasn't it? To be sure that ...


3

Try to install pkg-config. I met same trouble in Ubuntu 1804 on Windows Subsystem for Linux. I read configure script, and found the script uses pkg-config to check version of gnutls.


3

I believe that if system-configuration-features includes X11 then Emacs was compiled with X support. That value is set in configure by the HAVE_X11 variable being true (look for: emacs_config_features=), which in turn is based on window_system=x11 which you can trace back through a more complicated set of tests.


3

My solution was to create a virtual machine with Centos where I have admin rights, and compile emacs there. When building, I added a prefix to configure. That way make install put everything within a folder that mimicked the directory tree of the machine where I have no admin rights. Install Centos on a virtual machine and grab all dependencies. Get the ...


3

This line only applies to release tarballs (hence why it says "unpacked") which come with a configure script. For the git checkout you'll need to generate it with ./autogen.sh. Be sure to check out the README file for more instructions.


3

Dunno about a command-line switch, but: If you use library emacsbug+.el, which enhances standard library emacsbug.el, then you can use command ebp-insert-version with a prefix arg, to insert the complete version info, including some build info, in the current buffer. This is the same version info that is included when you use command report-emacs-bug. For ...


3

Here are various suggestions. No elc files. As stated below, compiling all of the lisp files accounts for at least 10% of the time. One way to disable that is to edit the loaddefs target in file lisp/Makefile and change that to: $(lisp)/loaddefs.el: $(LOADDEFS) true No compiler optimization or debugger symbol tables Currently, I'm ...


3

There is no graphical Emacs build for Linux without X, no. As suggested in the commentary, you can use textual Emacs instead and customize the parts interacting with the clipboard to use wl-clipboard instead.


3

When using the flag --without-ns, that means do not build Emacs specifically for the MacOS platform. How about using --with-ns instead, or no flag at all? The build script should automatically build Emacs for MacOS when building on that platform -- i.e., when not using --with-ns or --without-ns. The package Emacs.app will be in the nextstep folder of the ...


2

I had tried the instructions in emacs/nt/INSTALL last year for the 32-bit build but something went wrong (I don't remember what, exactly), so recently I tried the instructions for emacsbinw64 - it worked very well, and it was simpler to get the necessary libraries also. It uses MSYS2 and MinGW-w64 for a 64-bit build - the emacsbinw64 project provides ...


2

Complile without cairo. Worked for me.


2

You can inspect the variable system-configuration-options with C-h v system-configuration-options system-configuration-options is a variable defined in `C source code'. Its value is "" Documentation: String containing the configuration options Emacs was built with. In my case, the value is: "--host=x86_64-debian-linux-gnu --with-modules"


2

Emacs uses the "libpng-config" tool to locate PNG include files and libraries. So yes, if you have multiple versions installed you need to adjust PATH so that the one you want to be used, is. For other libraries, it's normally "pkg-config" that is consulted, for which there is the PKG_CONFIG_PATH environment variable. If Anaconda provides a pkg-config, it ...


2

The variable invocation-directory contains the directory in which the Emacs executable was found, so you can use (file-truename (expand-file-name "bin/etags" invocation-directory)) See also the question Can Emacs detect the path of its executable?.


2

First: do you need to run Emacs on that system? Emacs can access remote files easily. Typically you just run it on your local machine. If you only ever access the system remotely, it probably doesn't need Emacs. ARM covers a very wide range of system sizes, from appliances with only a few megabytes of memory to equivalents of a 10-year old PC such as the ...


2

make is a program often used to automate life-cycle of another program. Compiling, testing, packaging and installing would be examples of events in a program's life-cycle managed by make. Usually, it uses a configuration file, typically called Makefile, to describe what should happen during each event in the program's life-cycle. These descriptions are ...


2

On macOS, Emacs builds itself a self-contained application bundle by default. You can find it in the build tree via the output at the end of the ./configure step. You must run "make install" in order to test the built application. The installed application will go to nextstep/Emacs.app and can be run or moved from there. The application will be fully self-...


1

You may install emacs-plus from this: From that link: Note that by default emacs-plus builds the Cocoa version of Emacs with gnutls, imagemagick, librsvg and dynamic modules support by default.


1

In order to avoid conficts with the standard package you should give a custom name to the one you build, for example adding the suffix "local-build".


Only top voted, non community-wiki answers of a minimum length are eligible