From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:58726) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QPfZF-0004Gw-64 for qemu-devel@nongnu.org; Thu, 26 May 2011 14:45:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QPfZE-0006Yl-1U for qemu-devel@nongnu.org; Thu, 26 May 2011 14:45:57 -0400 Received: from mail-qw0-f45.google.com ([209.85.216.45]:44486) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QPfZD-0006Yc-VZ for qemu-devel@nongnu.org; Thu, 26 May 2011 14:45:56 -0400 Received: by qwj8 with SMTP id 8so638590qwj.4 for ; Thu, 26 May 2011 11:45:55 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Blue Swirl Date: Thu, 26 May 2011 21:45:35 +0300 Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] dynamically linked binaries under sparc-linux-user List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Artyom Tarasenko Cc: qemu-devel On Tue, May 24, 2011 at 10:42 PM, Artyom Tarasenko wr= ote: > 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) =3D 0 > 14004 brk(NULL) =3D 0x00063000 > 14004 access("/etc/ld.so.nohwcap",F_OK) =3D -1 errno=3D2 (No such file or= directory) > 14004 mmap(NULL,4096,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANONYMOUS,-1,0) > =3D 0x40a2c000 > 14004 access("/etc/ld.so.preload",R_OK) =3D -1 errno=3D2 (No such file or= directory) > 14004 open("/etc/ld.so.cache",O_RDONLY) =3D 3 > 14004 fstat64(3,0x409ff500) =3D 0 > 14004 mmap(NULL,195479,PROT_READ,MAP_PRIVATE,3,0) =3D 0x40a2d000 > 14004 close(3) =3D 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$ =C2=A0ll ../../debian-4.08r1-initrd/etc/ld.so.cache /etc/ld.so.ca= che > 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? I'm not sure. It could be possible to construct a blacklist of host files that may not be accessible or visible to the guest but that wouldn't very robust either. Chrooting into a 100% guest architecture system should work better.