qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Erik de Castro Lopo <1042388@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1042388] Re: qemu: Unsupported syscall: 257 (timer_create)
Date: Sat, 21 Dec 2013 08:09:08 -0000	[thread overview]
Message-ID: <20131221080908.7596.45692.malone@soybean.canonical.com> (raw)
In-Reply-To: 20120827193051.19884.38859.malonedeb@chaenomeles.canonical.com

I don't have a machine running Ubuntu. I onlu lodged a bug here because
this is the official bug tracker for Qemu.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1042388

Title:
  qemu: Unsupported syscall: 257 (timer_create)

Status in QEMU:
  Confirmed

Bug description:
  Running qemu-arm-static for git HEAD. When I try to install ghc from
  debian into my arm chroot I get:

  Setting up ghc (7.4.1-4) ...
  qemu: Unsupported syscall: 257
  ghc: timer_create: Function not implemented
  qemu: Unsupported syscall: 257
  ghc-pkg: timer_create: Function not implemented
  dpkg: error processing ghc (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   ghc
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1042388/+subscriptions

  parent reply	other threads:[~2013-12-21  8:15 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 19:30 [Qemu-devel] [Bug 1042388] [NEW] qemu: Unsupported syscall: 257 Erik de Castro Lopo
2012-08-27 20:57 ` [Qemu-devel] [Bug 1042388] Re: qemu: Unsupported syscall: 257 (timer_create) Peter Maydell
2012-08-27 21:33   ` Erik de Castro Lopo
2012-08-28  7:49     ` Peter Maydell
2012-08-28 13:23       ` Erik de Castro Lopo
2012-08-28  8:29 ` Riku Voipio
2012-09-19 10:40 ` Erik de Castro Lopo
2013-01-08 19:38 ` Matt Robinson
2013-01-10 21:36   ` Erik de Castro Lopo
2013-04-02 12:05 ` LocutusOfBorg
2013-04-03 21:26   ` Erik de Castro Lopo
2013-04-10  6:27 ` LocutusOfBorg
2013-04-10  8:13 ` Erik de Castro Lopo
2013-05-20 15:17 ` Predrag Radovic
2013-10-18  9:03 ` Erik de Castro Lopo
2013-10-18 23:50 ` Erik de Castro Lopo
2013-10-19 10:20 ` Erik de Castro Lopo
2013-12-20  0:54 ` Erik de Castro Lopo
2013-12-20  7:38 ` LocutusOfBorg
2013-12-20  9:40 ` Erik de Castro Lopo
2013-12-20  9:42 ` Erik de Castro Lopo
2013-12-20 14:13 ` LocutusOfBorg
2013-12-20 19:33 ` Erik de Castro Lopo
2013-12-21  7:54 ` LocutusOfBorg
2013-12-21  8:09 ` Erik de Castro Lopo [this message]
2013-12-21  8:29 ` Erik de Castro Lopo
2013-12-21  8:52 ` LocutusOfBorg
2014-01-14 11:13 ` Martin Pitt
2014-01-14 12:22 ` Ubuntu Foundations Team Bug Bot
2014-01-14 13:49 ` Martin Pitt
2014-01-15  3:30 ` Erik de Castro Lopo
2014-02-10 19:23 ` Serge Hallyn
2014-02-11  0:43 ` Erik de Castro Lopo
2014-08-09  4:39 ` Serge Hallyn
2014-08-09  6:15 ` Erik de Castro Lopo
2014-08-09 13:51   ` Peter Maydell
2014-08-09 14:46 ` Peter Maydell
2014-08-23  7:21 ` Erik de Castro Lopo
2015-09-23 16:49 ` Serge Hallyn
2016-09-02 17:43 ` Peter Maydell

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=20131221080908.7596.45692.malone@soybean.canonical.com \
    --to=1042388@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.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.
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).