public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mckinlay at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/28175] libgcj install tree should be relocatable
Date: Thu, 29 Jun 2006 18:33:00 -0000 [thread overview]
Message-ID: <20060629181002.28791.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28175-8711@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from mckinlay at redhat dot com 2006-06-29 18:10 -------
Using /proc/self/exe would only work for "gij" - we'd want a solution that can
work for native binaries as well, so figuring out the prefix based on
libgcj.so's location is probably better.
On Linux, this can be found with dl_iterate_phdr().
--
mckinlay at redhat dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mckinlay at redhat dot com
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2006-06-29 18:10:01
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28175
prev parent reply other threads:[~2006-06-29 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 0:28 [Bug libgcj/28175] New: " fitzsim at redhat dot com
2006-06-29 18:33 ` mckinlay at redhat dot com [this message]
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=20060629181002.28791.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).