unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Svante Signell <svante.signell@gmail.com>
To: "Paul Eggert" <eggert@cs.ucla.edu>,
	"Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: 24857@debbugs.gnu.org, 25081@debbugs.gnu.org
Subject: bug#24857: Anybody needs help to set up a qemu VM for GNU/Hurd?
Date: Thu, 08 Dec 2016 10:12:03 +0100	[thread overview]
Message-ID: <1481188323.9077.79.camel@gmail.com> (raw)
In-Reply-To: <03dd4752-ebf7-c36f-0f49-e255d1e649d0@cs.ucla.edu>

(Adding #24857 and Clement to the recipients list.)

On Wed, 2016-12-07 at 16:45 -0800, Paul Eggert wrote:
> On 12/07/2016 03:00 PM, Svante Signell wrote:
> > Hi, adding emacs-devel to the recipients
> 
> I'm not sure emacs-devel is worth bothering over all the details here, 
> so I'll drop it from the CC: list for now. We can send emacs-devel a 
> summary later as needed.

OK!

> > 
> > I normally use:
> > qemu-system-x86_64 -enable-kvm -m 2048 -net nic,model=rtl8139 -net
> > user,hostfwd=tcp::<port>-:22 -drive
> > cache=writeback,index=0,media=disk,file=<whatever>.img
> 
> Thanks, that wasn't obvious, I used that. Perhaps make it part of the 
> brief HOWTO?

I'll propose that to people who can make these changes.

> > This is expected, since qemu does not know exactly in what format the file
> > is
> > in. Maybe just ignore that warning for now? I (and others) do.
> > 
> 
> I'm a fan of fixing warnings; otherwise I find that I stop paying 
> attention to them. Surely there's some option I can give to qemu to 
> suppress the warning, and that could be part of the HOWTO?

I still haven't bothered to find out which option to pass to qemu. Maybe its
useful to find out and add it to the HOWTO too.

> > It might be easier to use the debian tools: 
> 
> I assume these commands need to be run as root on the guest.
> 
> > apt-get update
> > apt-get dist-upgrade
> 
> These work, thanks. The latter takes a looong time. Perhaps this should 
> be written down too.

Noted!

> > apt-get build-dep emacs24/emacs25

I was too brief here:
apt-get build-dep emacs24
apt-get build-dep emacs25

> This fails with 'Reading package lists... Done
> E: Unable to find a source package for emacs24/emacs25'. I forged ahead 
> by running just "apt-get build-dep emacs25" but that failed with:
> 
> E: Failed to fetch 
> http://httpredir.debian.org/debian/pool/main/libx/libxdmcp/libxdmcp-dev_1.1.2-
> 1.1_hurd-i386.deb 
> Error reading from server. Remote end closed connection [IP: 
> 5.153.231.35 80]
> E: Unable to fetch some archives, maybe run apt-get update or try with 
> --fix-missing?
> E: Failed to process build dependencies
> 
> I tried running "apt-get build-dep emacs25" again. This time it finished.

Probably just a network glitch.

> > apt-get source emacs24/emacs25

As above:
apt-get source emacs24
apt-get source emacs25

> I don't want to do this, as I want to build from the master branch. I 
> did that, with plain 'configure; make'.

So you built from the tarball, right?

> Emacs built and eventually attempted to dump itself, and while it was 
> doing so, the operating system crashed. When I attempted to reboot, fsck 
> failed. I ran fsck -y by hand (took a while) and rebooted. When the OS 
> came back up, temacs was size-0, so I removed it and ran 'make' again. 
> This time it worked, in the sense that I can now run Emacs in a tty window.

I've also successfully built different emacs tarballs and git repos. The problem
is building again, or worse: to build a Debian package, which copies the whole
emacs tree into three different build directories: build-x, build-nox, build-
lucid, as well as rebuilding all *.elc files. See bug #24857, especially
comments #86,89,92,95 of that bug, for more info where Clément Pit--Claudel did
the same as you.

> So, it sounds like we can declare victory against this bug, at least for 
> the master branch. At least, it worked for me, if you ignore the OS 
> crashing during the build. Possibly the crash was because I didn't 
> reboot after the 'apt-get dist-upgrade' (you didn't say to reboot, so I 
> didn't....).

Sorry, I should have added <reboot> after dist-upgrade especially when
gnumach/hurd/glibc are updated.







  reply	other threads:[~2016-12-08  9:12 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 15:20 bug#24857: emacs24/25 FTBFS since a long time on GNU/Hurd Paul Eggert
2016-11-02 16:46 ` Eli Zaretskii
2016-11-02 17:38   ` Svante Signell
2016-11-10 11:57     ` Svante Signell
2016-11-10 16:00       ` Eli Zaretskii
2016-11-10 20:35         ` Svante Signell
2016-11-11  7:48           ` Eli Zaretskii
2016-11-11  9:50             ` Svante Signell
2016-11-11 10:06               ` Eli Zaretskii
2016-11-11 10:32                 ` Svante Signell
2016-11-11 10:59                   ` Eli Zaretskii
2016-11-11 11:18                     ` Svante Signell
2016-11-11 14:03                       ` Eli Zaretskii
2016-11-11 15:04                         ` Svante Signell
2016-11-11 15:33                           ` Eli Zaretskii
2016-11-21 16:57                             ` Eli Zaretskii
2017-07-14 12:21                               ` Paul Eggert
2017-09-02 13:45                                 ` Eli Zaretskii
2017-09-02 14:10                                   ` Svante Signell
2017-09-02 14:27                                     ` Eli Zaretskii
2017-09-02 14:43                                       ` Svante Signell
2017-09-02 15:04                                         ` Eli Zaretskii
2017-09-02 18:11                                         ` Paul Eggert
2016-11-11 11:03                   ` Eli Zaretskii
2016-11-11 11:33                     ` Svante Signell
2016-11-11 14:06                       ` Eli Zaretskii
2016-11-12 18:12                       ` Paul Eggert
2016-11-04 20:17 ` bug#24857: Anybody needs help to set up a qemu VM for GNU/Hurd? Svante Signell
2016-11-29 21:14   ` Clément Pit--Claudel
2016-12-01 14:52   ` bug#25081: " Svante Signell
2016-12-01 16:48     ` bug#24857: " Clément Pit--Claudel
2016-12-01 17:29       ` Svante Signell
2016-12-01 19:25         ` Glenn Morris
2016-12-01 22:09           ` Svante Signell
2016-12-07 22:36     ` bug#25081: " Paul Eggert
2016-12-07 23:00       ` Svante Signell
     [not found]       ` <1481151606.9077.59.camel@gmail.com>
2016-12-08  0:45         ` Paul Eggert
2016-12-08  9:12           ` Svante Signell [this message]
2016-12-08 15:50             ` bug#24857: " Paul Eggert
2016-12-08  0:54       ` bug#25081: " Clément Pit--Claudel
2016-12-08  1:01         ` Paul Eggert
2016-12-08  1:15           ` Clément Pit--Claudel
2016-12-08  1:05         ` Glenn Morris
2017-11-02  1:10   ` bug#24857: " Noam Postavsky
2017-11-02 17:49   ` Noam Postavsky
2018-01-06 23:20     ` Noam Postavsky
2016-12-08 17:01 ` bug#24857: Sorry, reopening this bug Svante Signell
2016-12-08 17:25   ` Eli Zaretskii
2016-12-08 17:34     ` Svante Signell

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=1481188323.9077.79.camel@gmail.com \
    --to=svante.signell@gmail.com \
    --cc=24857@debbugs.gnu.org \
    --cc=25081@debbugs.gnu.org \
    --cc=clement.pit@gmail.com \
    --cc=eggert@cs.ucla.edu \
    /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).