public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: peter_broadhurst@ml.com To: gcc-gnats@gcc.gnu.org Subject: c++/5721: link errors when using typedef struct {...}A; Date: Mon, 18 Feb 2002 08:16:00 -0000 [thread overview] Message-ID: <20020218161017.32048.qmail@sources.redhat.com> (raw) >Number: 5721 >Category: c++ >Synopsis: link errors when using typedef struct {...}A; >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Feb 18 08:16:06 PST 2002 >Closed-Date: >Last-Modified: >Originator: peter_broadhurst@ml.com >Release: 3.0.3 >Organization: >Environment: sparc-sun-solaris2.6 i386-redhat-linux (redhat 7.1) >Description: The files below give a link time error (undefined symbol A::f()) when compiled and linked. If the definition of A::f() is moved to the same file where it is used, then the problem disappears. if "struct A { void f(void); }; " is used, then the problem disappears. nm indicates that a local-only definition of A::F() is placed in typedeflinkbug2.o. Works in gcc 2.8.1 ==> typedeflinkbug.h <== typedef struct { void f(void); } A; ==> typedeflinkbug1.cpp <== #include "typedeflinkbug.h" int main(int,char**) { A a; a.f(); return 0; } ==> typedeflinkbug2.cpp <== #include "typedeflinkbug.h" void A::f(void) { } >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-02-18 16:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-18 8:16 peter_broadhurst [this message] 2002-02-22 19:28 rodrigc 2002-04-20 13:13 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=20020218161017.32048.qmail@sources.redhat.com \ --to=peter_broadhurst@ml.com \ --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: linkBe 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).