From: Artyom Tarasenko <atar4qemu@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>, Blue Swirl <blauwirbel@gmail.com>
Subject: [Qemu-devel] dynamically linked binaries under sparc-linux-user
Date: Tue, 24 May 2011 21:42:30 +0200 [thread overview]
Message-ID: <BANLkTimPHrdyVFfyCphoqMUvahDysyh58Q@mail.gmail.com> (raw)
Should it be possible to use dynamically linked binaries under
sparc*-linux-user?
Under qemu-system-sparc the Debian 4.08r1 initrd works fine, but:
master$ sparc-linux-user/qemu-sparc -strace -L
../debian-4.08r1-initrd/ ../debian-4.08r1-initrd/bin/busybox
14004 uname(0x409ffbae) = 0
14004 brk(NULL) = 0x00063000
14004 access("/etc/ld.so.nohwcap",F_OK) = -1 errno=2 (No such file or directory)
14004 mmap(NULL,4096,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS,-1,0)
= 0x40a2c000
14004 access("/etc/ld.so.preload",R_OK) = -1 errno=2 (No such file or directory)
14004 open("/etc/ld.so.cache",O_RDONLY) = 3
14004 fstat64(3,0x409ff500) = 0
14004 mmap(NULL,195479,PROT_READ,MAP_PRIVATE,3,0) = 0x40a2d000
14004 close(3) = 0
Segmentation fault
The strange thing here is that it loads ld.so.cache. The guest fs
doesn't have it, but the host does:
master$ ll ../../debian-4.08r1-initrd/etc/ld.so.cache /etc/ld.so.cache
ls: cannot access ../../debian-4.08r1-initrd/etc/ld.so.cache: No such
file or directory
-rw-r--r--. 1 root root 195479 2011-03-17 13:48 /etc/ld.so.cache
Isn't this wrong?
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
next reply other threads:[~2011-05-24 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 19:42 Artyom Tarasenko [this message]
2011-05-26 18:45 ` [Qemu-devel] dynamically linked binaries under sparc-linux-user Blue Swirl
2011-05-28 23:32 ` Artyom Tarasenko
2011-06-04 8:30 ` Blue Swirl
2011-06-05 20:28 ` Artyom Tarasenko
2011-06-12 21:08 ` Blue Swirl
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=BANLkTimPHrdyVFfyCphoqMUvahDysyh58Q@mail.gmail.com \
--to=atar4qemu@gmail.com \
--cc=blauwirbel@gmail.com \
--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).