public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/15535] Rust binary doesn't loaded on i686
Date: Wed, 29 May 2013 03:29:00 -0000 [thread overview]
Message-ID: <bug-15535-131-cKjtsyvkeP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15535-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15535
--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to libbkmz from comment #3)
> I'm not understand. What does you mean under *new* dynamic linker?
> What rpath should I use?
If you need help building a new glibc and testing the newly built dynamic
linker please post your question to libc-help@sourceware.org. That way we can
have a longer and more detailed discussion that is allowed in a bug report.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-05-29 3:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 17:49 [Bug dynamic-link/15535] New: Rust binaries " libbkmz.dev at gmail dot com
2013-05-25 17:51 ` [Bug dynamic-link/15535] " libbkmz.dev at gmail dot com
2013-05-25 17:53 ` [Bug dynamic-link/15535] Rust binary " libbkmz.dev at gmail dot com
2013-05-25 17:56 ` corey at octayn dot net
2013-05-28 21:07 ` carlos at redhat dot com
2013-05-29 3:27 ` libbkmz.dev at gmail dot com
2013-05-29 3:29 ` carlos at redhat dot com [this message]
2014-02-06 18:23 ` jsm28 at gcc dot gnu.org
2014-06-13 13:49 ` 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-15535-131-cKjtsyvkeP@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).