public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: daniel.elstner@gmx.net
To: gcc-gnats@gcc.gnu.org
Subject: c++/3301: gcc 3.0.1 20010618 breaks kdelibs-2.1.2 build
Date: Wed, 20 Jun 2001 12:46:00 -0000 [thread overview]
Message-ID: <20010620194303.22448.qmail@sourceware.cygnus.com> (raw)
>Number: 3301
>Category: c++
>Synopsis: gcc 3.0.1 20010618 breaks kdelibs-2.1.2 build
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Jun 20 12:46:03 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Daniel Elstner
>Release: gcc 3.0.1 20010618
>Organization:
>Environment:
i686-pc-linux-gnu
>Description:
Linking of artsd fails with following errors:
soundserver_impl.o(.gnu.linkonce.d._ZTCN4Arts16SoundServer_implE52_NS_16SoundServer_skelE+0x204): undefined reference to `virtual thunk to Arts::SoundServer_base::_defaultPortsIn() const'
soundserver_impl.o(.gnu.linkonce.d._ZTCN4Arts16SoundServer_implE52_NS_16SoundServer_skelE+0x208): undefined reference to `virtual thunk to Arts::SoundServer_base::_defaultPortsOut() const'
soundserver_impl.o(.gnu.linkonce.d._ZTCN4Arts16SoundServer_implE52_NS_16SoundServer_skelE+0x20c): undefined reference to `virtual thunk to Arts::SoundServer_base::_cast(unsigned long)'
It works fine with gcc-3.0 release. Tried it with binutils 2.11 / 2.11.2.
I'm sorry for not providing a test case or some files from the package. Since it's a linker failure, I just don't know what kind of information you need.
>How-To-Repeat:
start make in arts/soundserver
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-06-20 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 12:46 daniel.elstner [this message]
2001-08-12 13:06 rodrigc
2001-08-17 14:26 Craig Rodrigues
2001-08-17 14:56 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=20010620194303.22448.qmail@sourceware.cygnus.com \
--to=daniel.elstner@gmx.net \
--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).