public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/46191] Non-absolute names in libgcc_s.so
Date: Wed, 27 Oct 2010 02:04:00 -0000	[thread overview]
Message-ID: <20101027020400.KB1YgKLRAqgPgmKXcuZkIbEjrCNAkslazw7iRGLE5Es@z> (raw)
In-Reply-To: <bug-46191-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46191

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-10-27 02:04:30 UTC ---
Using absolute names is undesirable too, because then gcc is not actually
relocatable.  Guess we want something like $ORIGIN relative path if $ORIGIN or
something similar expands to the directory the linker script was found in.


  reply	other threads:[~2010-10-27  2:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26 22:27 [Bug target/46191] New: " schwab@linux-m68k.org
2010-10-27  2:04 ` jakub at gcc dot gnu.org [this message]
2010-10-27  8:33 ` [Bug target/46191] " schwab@linux-m68k.org
2010-10-27 11:07 ` ibolton at gcc dot gnu.org
2010-10-27 11:09 ` ibolton at gcc dot gnu.org
2010-10-27 12:02 ` [Bug target/46191] [4.5/4.6 regression] " joseph at codesourcery dot com
2010-10-27 12:44 ` jakub at gcc dot gnu.org
2010-11-03 15:40 ` rguenth at gcc dot gnu.org
2010-11-08 12:59 ` schwab@linux-m68k.org
2010-11-12 14:21 ` rguenth at gcc dot gnu.org
2010-12-16 13:21 ` rguenth at gcc dot gnu.org
2011-04-28 15:35 ` [Bug target/46191] [4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2012-07-02 12:09 ` [Bug target/46191] [4.5/4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2012-09-10 20:15 ` [Bug target/46191] [4.6/4.7/4.8 " schwab at gcc dot gnu.org
2013-04-12 15:16 ` [Bug target/46191] [4.7 " jakub at gcc dot gnu.org
2014-06-12 12:58 ` rguenth at gcc dot gnu.org

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=20101027020400.KB1YgKLRAqgPgmKXcuZkIbEjrCNAkslazw7iRGLE5Es@z \
    --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).