zsh-workers
 help / color / mirror / code / Atom feed
From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-workers@zsh.org
Subject: Re: zpty-related testsuite failures if building in a chroot on a host running systemd 220 as init system
Date: Fri, 12 Jun 2015 22:52:28 +0200	[thread overview]
Message-ID: <20150612205228.GQ4744@sym.noone.org> (raw)
In-Reply-To: <20150606184832.GB4744@sym.noone.org>

Hi,

On Sat, Jun 06, 2015 at 08:48:33PM +0200, Axel Beckert wrote:
> > > * systemd is at version 220. (The version of udev doesn't seem to
> > >   matter and compiling under systemd 215 works fine.)
> > 
> > Are there any differences in the results of configure between the two
> > versions of systemd or is it only when the tests are run that there's a
> > difference.
> 
> Will have to figure out. I though suspect that the chroot behaves
> differently under systemd 220. One indicator for that is this error
> message in chroot cleanup after the (failed) build:
> 
> W: Could not unmount dev/pts: umount:
> /var/cache/pbuilder/build//17909/dev/pts: not mounted

Actually if I call "mount -t devpts none /dev/pts" inside the chroot
before running the testsuite (even if ran after building zsh in the
chroot), the testsuite passes.

So for some reason the testsuite fails if /dev/pts is just an empty
directory, i.e. /dev/pts/ptmx does not exist in the chroot, but
/dev/pts does.

		Kind regards, Axel
-- 
/~\  Plain Text Ribbon Campaign                   | Axel Beckert
\ /  Say No to HTML in E-Mail and News            | abe@deuxchevaux.org  (Mail)
 X   See http://www.nonhtmlmail.org/campaign.html | abe@noone.org (Mail+Jabber)
/ \  I love long mails: http://email.is-not-s.ms/ | http://abe.noone.org/ (Web)


  reply	other threads:[~2015-06-12 21:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 15:02 Axel Beckert
2015-06-05 15:29 ` Axel Beckert
2015-06-06 10:49 ` Oliver Kiddle
2015-06-06 18:48   ` Axel Beckert
2015-06-12 20:52     ` Axel Beckert [this message]
2015-06-13 10:48       ` Axel Beckert
2015-06-13 17:01         ` Peter Stephenson
2015-06-13 17:43           ` Bart Schaefer
2015-06-15 10:55           ` Axel Beckert
2015-06-16  0:07             ` Bart Schaefer

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

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

  git send-email \
    --in-reply-to=20150612205228.GQ4744@sym.noone.org \
    --to=abe@deuxchevaux.org \
    --cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).