public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9872: temporary destructor not called? Date: Fri, 28 Feb 2003 00:36:00 -0000 [thread overview] Message-ID: <20030228003600.8204.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9872; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: Sandor Kovacs <sandor@ctjapan.com> Cc: gcc-bugs@gcc.gnu.org, <sakovacs@freemail.hu>, <gcc-gnats@gcc.gnu.org> Subject: Re: c++/9872: temporary destructor not called? Date: Thu, 27 Feb 2003 18:35:21 -0600 (CST) Sandor, I attached your preprocessed source. Thanks for sending them in. However... > If I've missed something or you need further info please let me know; ...yes, we are missing something: > gcc -L/usr/lib/qt3/lib -lqt-mt bug.o -o bug You are linking with libqt-mt.so. What we need is a _self-contained_ testcase, i.e. something that we can test without additional libraries. If we don't have that, it is impossible to find out whether the problem is in the compiler itself, or in the code that is in the library that is being linked in. Please try to pack everything into one file, including the necessary .cpp files from qt, such that it can be compiled without linking together several .o or .so files. Thanks Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-02-28 0:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-28 0:36 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-28 2:06 Sandor Kovacs 2003-02-28 1:56 Sandor Kovacs 2003-02-28 0:26 Sandor Kovacs 2003-02-27 15:32 bangerth 2003-02-27 4:56 sakovacs
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=20030228003600.8204.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).