unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.graziosi@alice.it>
To: 25221@debbugs.gnu.org
Subject: bug#25221: Packages manager not working in WSL emacs-25 build
Date: Sun, 18 Dec 2016 14:07:44 +0100	[thread overview]
Message-ID: <ddeac3b0-3c33-f914-e1a0-ffef19bf2556@alice.it> (raw)

I recently enabled and installed WSL (Windows Subsystem for Linux) in 
Windows 10 [1] and so tried to build Emacs.

Building Emacs master hangs [2]. So tried emacs-25 branch (+release and 
testing). This branch builds if one adopts the work around suggested in 
/et/PROBLEMS and from the WEB [3]:

echo 0 | sudo tee /proc/sys/kernel/randomize_va_space
./autogen.sh
./configure --prefix=/opt/emacs --without-x
make...

It also seems to work but trying to install packages from MELPA/ELPA fails.

More precisely, in emacs25:

M-x package-list-packages

After the "Package refresh done" I cannot type anything nor I can quit 
(C-x C-c). If I do, for example pressing the down arrow key, in the 
packages buffer I see something like this

[...]
[1]+  Stopped                 emacs25ailable  melpa      No description 
available...
angelo@MYPC~   20151026.1233 available  melpa      play 2048 in Emacs..
$ 4clojure           20131014.1507 available  melpa..
[...]

At this point I can only try to kill Emacs. It is as if Emacs were 
reduced to background (C-z), and a 'fg' seems to resurrect it but is 
unusable (I have to close the WSL bash window).

Now, at the moment, enabling and installing WSL installs Ubuntu 14.04 
and one can install other Ubuntu packages with apt-get. So I installed 
the emacs24-nox packages which works without this Packages manager issue!

Then for sanity check I did a build of emacs-24.3.tar.gz (the same 
version offered by WSL-Ubuntu) and it works as expected (also the 
packages Manager).

So the issue seems to regards only emacs-25 branch.


Ciao,
  Angelo.


-----
[1] https://msdn.microsoft.com/it-it/commandline/wsl/install_guide
     https://msdn.microsoft.com/it-it/commandline/wsl/faq

[2] http://lists.gnu.org/archive/html/emacs-devel/2016-12/msg00427.html

[3] 
http://stackoverflow.com/questions/38905344/windows-bash-emacs-build-fail-memory-protection-enabled





             reply	other threads:[~2016-12-18 13:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-18 13:07 Angelo Graziosi [this message]
2016-12-25  1:14 ` bug#25221: Packages manager not working in WSL emacs-25 build Paul Eggert
2016-12-25  1:35   ` Angelo Graziosi
2016-12-25  3:33     ` Eli Zaretskii
2016-12-25  8:03     ` Paul Eggert
2016-12-25 12:46       ` Angelo Graziosi
2017-07-17  2:09         ` npostavs
2017-07-17 12:41           ` Angelo Graziosi
     [not found]             ` <da977c87-64a4-9557-8b99-b707bc8e0d4d@openmailbox.org>
2017-07-19 15:10               ` Angelo Graziosi
2017-04-14 22:32 ` Angelo Graziosi

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=ddeac3b0-3c33-f914-e1a0-ffef19bf2556@alice.it \
    --to=angelo.graziosi@alice.it \
    --cc=25221@debbugs.gnu.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/emacs.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).