public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lfs4pi at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/15006] Libraries in ld.so.cache ignored by ld-linux-armhf.so.3 on armv6l
Date: Sun, 13 Jan 2013 20:30:00 -0000 [thread overview]
Message-ID: <bug-15006-131-XUL8h1yNt1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15006-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15006
--- Comment #19 from lfs4pi at gmail dot com 2013-01-13 20:29:48 UTC ---
(In reply to comment #18)
> Alright, you can grab the QEMU image here:
> http://circu.it/pilfs/glibc217.ext4.xz
> And a suitable kernel here: http://circu.it/pilfs/pilfs-qemu-kernel.zip
>
> Start QEMU something like so: qemu-system-arm -M versatilepb -cpu arm1176 -m
> 256 -kernel kernel.img -drive file=glibc217.ext4,cache=none -append
> "root=/dev/sda rootfstype=ext4"
>
> Login as root, password "pilfs".
>
> Let me know if you have any problems running the images.
New QEMU disk image with unstripped binaries, gdb and compiled glibc source
tree in /sources:
http://circu.it/pilfs/glibc217debug.ext4.xz (408 Mb)
Hope it proves helpful.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-01-13 20:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 0:50 [Bug dynamic-link/15006] New: " lfs4pi at gmail dot com
2013-01-09 0:51 ` [Bug dynamic-link/15006] " lfs4pi at gmail dot com
2013-01-09 13:55 ` steve.mcintyre at linaro dot org
2013-01-09 14:39 ` lfs4pi at gmail dot com
2013-01-09 14:49 ` steve.mcintyre at linaro dot org
2013-01-09 15:03 ` lfs4pi at gmail dot com
2013-01-09 15:46 ` steve.mcintyre at linaro dot org
2013-01-09 16:02 ` lfs4pi at gmail dot com
2013-01-09 16:04 ` lfs4pi at gmail dot com
2013-01-09 16:06 ` lfs4pi at gmail dot com
2013-01-10 0:33 ` jplum at archlinuxarm dot org
2013-01-10 11:22 ` steve.mcintyre at linaro dot org
2013-01-10 11:29 ` steve.mcintyre at linaro dot org
2013-01-10 12:37 ` lfs4pi at gmail dot com
2013-01-10 13:50 ` steve.mcintyre at linaro dot org
2013-01-10 14:41 ` jplum at archlinuxarm dot org
2013-01-11 4:01 ` kevin at archlinuxarm dot org
2013-01-11 18:23 ` steve.mcintyre at linaro dot org
2013-01-11 18:36 ` jplum at archlinuxarm dot org
2013-01-11 18:41 ` lfs4pi at gmail dot com
2013-01-11 22:16 ` lfs4pi at gmail dot com
2013-01-13 20:30 ` lfs4pi at gmail dot com [this message]
2013-01-23 18:25 ` steve.mcintyre at linaro dot org
2013-01-23 20:08 ` kevin at archlinuxarm dot org
2013-01-23 20:31 ` joseph at codesourcery dot com
2013-01-27 19:45 ` pbrobinson at gmail dot com
2013-01-28 20:02 ` carlos at systemhalted dot org
2013-01-29 16:57 ` fedux at lugmen dot org.ar
2013-02-06 19:52 ` carlos at redhat dot com
2013-02-07 5:14 ` carlos at redhat dot com
2013-02-08 17:33 ` carlos at redhat dot com
2014-02-16 19:41 ` jackie.rosen at hushmail dot com
2014-05-28 19:42 ` schwab at sourceware dot org
2014-06-13 18:54 ` fweimer at redhat dot com
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=bug-15006-131-XUL8h1yNt1@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).