public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/16592] New: Ada tools don't use the newly built shared libraries
Date: Fri, 16 Jul 2004 16:07:00 -0000	[thread overview]
Message-ID: <20040716160714.16592.hjl@lucon.org> (raw)

Some ada tools are linked against libgcc_s.so.1:

[hjl@gnu-20 gcc]$ ldd ./gnatmake
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000002a9566b000)
        libc.so.6 => /lib64/tls/libc.so.6 (0x0000002a95776000)
        /lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2
(0x0000002a95556000)

But they are used like

../../gnatmake -c -I../rts -I. -I/net/gnu/export/gnu/src/gcc-3.4/gcc/gcc/ada
gnatchop --GCC="../../xgcc -B../../ -g      -gnatpg -gnata"

The newly built libgcc_s.so.1 is never used.

-- 
           Summary: Ada tools don't use the newly built shared libraries
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ada
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: hjl at lucon dot org
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2004-07-16 16:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16 16:07 hjl at lucon dot org [this message]
2004-07-16 18:25 ` [Bug ada/16592] " pinskia at gcc dot gnu dot org
2004-07-16 18:28 ` hjl at lucon dot org
2004-07-19  4:52 ` hjl at lucon dot org
2004-07-19 15:35 ` hjl at lucon dot org
2004-07-19 15:36 ` hjl at lucon dot org
2004-07-19 15:45 ` hjl at lucon dot org
2004-07-19 15:53 ` hjl at lucon dot org
2004-07-19 15:53 ` hjl at lucon dot org
2004-09-15 21:59 ` hjl at lucon dot org
2005-02-10 19:08 ` cvs-commit at gcc dot gnu dot org
2005-02-10 19:24 ` charlet at gcc dot gnu dot 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=20040716160714.16592.hjl@lucon.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).