public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Bailey <jbailey@oasis.zugzug.com>
To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: c++/3389: gcc-3.0 doesn't build shared C++ library on i386-pc-gnu
Date: Sat, 23 Jun 2001 12:36:00 -0000	[thread overview]
Message-ID: <200106231928.f5NJS1rE003718@oasis.zugzug.com> (raw)

>Number:         3389
>Category:       c++
>Synopsis:       gcc-3.0 doesn't build shared C++ library on i386-pc-gnu
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 23 12:36:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Jeff Bailey
>Release:        3.0 20010426 (Debian prerelease) (Debian testing/unstable)
>Organization:
>Environment:

	
host: i386-pc-gnu
build: i386-pc-gnu
target: i386-pc-gnu
configured with: ../src/configure -v --enable-languages=c,c++,f77,proto,objc --prefix=/usr --infodir=/share/info --mandir=/share/man --enable-shared --with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-long --enable-nls --without-x --without-included-gettext --disable-checking --with-cpp-install-dir=bin i386-gnu

>Description:
	libstdc++3 doesn't generate shared library.
>How-To-Repeat:
	Consistent in i386-pc-gnu
>Fix:
	The following patch works, although I think perhaps they're supposed
	to be in alphabetical order.

--- ltcf-cxx.old        Wed Jun 20 00:29:07 2001
+++ ltcf-cxx.sh Wed Jun 20 00:29:32 2001
@@ -313,6 +313,8 @@
         ;;
     esac
     ;;
+  gnu*)
+  ;;
   linux*)
     case $cc_basename in
       KCC)
@@ -767,6 +769,8 @@
            ;;
       esac
       ;;
+    gnu*)
+    ;;
     linux*)
       case $cc_basename in
         KCC)
											
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-06-23 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-23 12:36 Jeff Bailey [this message]
2001-06-26 13:34 aoliva
2001-10-29  7:58 rodrigc

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=200106231928.f5NJS1rE003718@oasis.zugzug.com \
    --to=jbailey@oasis.zugzug.com \
    --cc=debian-gcc@lists.debian.org \
    --cc=gcc-gnats@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).