All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <1835839@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1835839] Re: qemu-user: $0 incorrectly always reports absolute path
Date: Thu, 17 Jun 2021 07:07:04 -0000	[thread overview]
Message-ID: <162391362449.16865.7957764889319255243.malone@gac.canonical.com> (raw)
In-Reply-To: 156262578461.2222.11301272429426949561.malonedeb@wampee.canonical.com

Laurent's patch has been included here:
https://gitlab.com/qemu-project/qemu/-/commit/6e1c0d7b951e19c53b8467e8bc4b71ee73a394ea
So I assume we can mark this as fixed now.

** Changed in: qemu
       Status: Incomplete => Fix Released

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

Title:
  qemu-user: $0 incorrectly always reports absolute path

Status in QEMU:
  Fix Released

Bug description:
  We just ran into an issue with the Perl package on Debian/m68k when
  being built with qemu-user [1].

  The problem can be boiled down to qemu-user always reporting absolute
  paths for the shell variable $0 no matter on how the command was
  invoked.

  A simple reproducer is this:

  On normal system (no emulation):

  root@nofan:~> sh -c 'echo $0'
  sh
  root@nofan:~>

  On qemu-user:

  (sid-m68k-sbuild)root@nofan:/# sh -c 'echo $0'
  /bin/sh
  (sid-m68k-sbuild)root@nofan:/#

  > [1] https://lists.debian.org/debian-68k/2019/07/msg00007.html

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


      parent reply	other threads:[~2021-06-17  7:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08 22:43 [Qemu-devel] [Bug 1835839] [NEW] qemu-user: $0 incorrectly always reports absolute path John Paul Adrian Glaubitz
2019-07-09 11:54 ` [Qemu-devel] [Bug 1835839] " Laurent Vivier
2019-07-09 12:12   ` John Paul Adrian Glaubitz
2019-07-09 12:51     ` Laurent Vivier
2019-07-09 12:51       ` Laurent Vivier
2019-07-09 13:07       ` John Paul Adrian Glaubitz
2019-07-09 14:01         ` Laurent Vivier
2019-07-09 14:01           ` Laurent Vivier
2019-07-09 15:09           ` John Paul Adrian Glaubitz
2019-07-09 15:11             ` John Paul Adrian Glaubitz
2019-07-09 15:25             ` Laurent Vivier
2019-07-09 15:25               ` Laurent Vivier
2019-07-09 12:16 ` Peter Maydell
2019-07-09 13:00   ` Laurent Vivier
2019-07-09 13:47   ` Laurent Vivier
2021-04-22  7:05 ` Thomas Huth
2021-06-17  7:07 ` Thomas Huth [this message]

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=162391362449.16865.7957764889319255243.malone@gac.canonical.com \
    --to=1835839@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.