From: bananaapple <webberapple@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1531352] Re: QEMU_LD_PREFIX PATH not work on loading library
Date: Wed, 06 Jan 2016 02:09:22 -0000 [thread overview]
Message-ID: <20160106020923.24248.28312.launchpad@soybean.canonical.com> (raw)
In-Reply-To: 20160106010526.4703.56064.malonedeb@chaenomeles.canonical.com
** Description changed:
run qemu with QEMU_LD_PREFIX argument will not load the library in the PATH.
- Ex: I use debootstrap to download the library of i386 architecture
+ Example: I use debootstrap to download the library of i386 architecture
And use -L point to the path.
But not load the library from that directory.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1531352
Title:
QEMU_LD_PREFIX PATH not work on loading library
Status in QEMU:
New
Bug description:
run qemu with QEMU_LD_PREFIX argument will not load the library in the PATH.
Example: I use debootstrap to download the library of i386 architecture
And use -L point to the path.
But not load the library from that directory.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1531352/+subscriptions
next prev parent reply other threads:[~2016-01-06 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 1:05 [Qemu-devel] [Bug 1531352] [NEW] QEMU_LD_PREFIX PATH not work on loading library bananaapple
2016-01-06 2:09 ` bananaapple [this message]
2016-01-06 7:39 ` [Qemu-devel] [Bug 1531352] Re: QEMU_LD_PREFIX PATH loading library is not in the correct order bananaapple
2016-01-06 7:55 ` [Qemu-devel] [Bug 1531352] Re: QEMU_LD_PREFIX not load correct library order in the PATH bananaapple
2016-01-06 8:24 ` bananaapple
2016-01-06 11:58 ` bananaapple
2020-11-19 16:22 ` Thomas Huth
2021-01-19 4:17 ` Launchpad Bug Tracker
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=20160106020923.24248.28312.launchpad@soybean.canonical.com \
--to=webberapple@gmail.com \
--cc=1531352@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).