public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kunert at physik dot tu-dresden dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/13707] New: libstdc++.a goes to the wrong directory
Date: Fri, 16 Jan 2004 14:55:00 -0000	[thread overview]
Message-ID: <20040116145520.13707.kunert@physik.tu-dresden.de> (raw)

During installation, everything goes to version specific directories.
Except libstdc++.a, which goes to /opt/lib overwriting any former library of the
same name. Of course one can work around that problem by copying that file next
to libgcc.a or fiddling with the configure options, but it is annoying to
recompile GCC 3.2 just because its libstdc++.a got overwritten.

Reading specs from /opt/lib/gcc/i686-pc-linux-gnu/3.4.0/specs
Configured with: ../configure --enable-shared --program-suffix=34
--disable-checking --with-arch=pentiumpro --prefix=/opt
--enable-languages=c,c++,f77 --enable-__cxa_atexit
Thread model: posix
gcc version 3.4.0 20040116 (experimental)

-- 
           Summary: libstdc++.a goes to the wrong directory
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: kunert at physik dot tu-dresden dot de
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2004-01-16 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16 14:55 kunert at physik dot tu-dresden dot de [this message]
2004-01-16 16:43 ` [Bug libstdc++/13707] " pinskia at gcc dot gnu dot org
2004-01-17 10:37 ` kunert at physik dot tu-dresden dot de
2004-01-17 19:11 ` pinskia 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=20040116145520.13707.kunert@physik.tu-dresden.de \
    --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).