public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "phil at nwl dot cc" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/42734] trivial use of std::thread fails with "pure virtual method called"
Date: Sat, 16 Jan 2010 01:08:00 -0000	[thread overview]
Message-ID: <20100116010803.2080.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42734-18664@http.gcc.gnu.org/bugzilla/>



------- Comment #27 from phil at nwl dot cc  2010-01-16 01:08 -------
(In reply to comment #26)
> Hey, I'm telling you the way we all library maintainers (like me) and users
> check the library: they all fetch everything (either mainline or 4_4-branch, or
> whatever) via svn, make, make check. Now you want to do something else, you
> want to check the compiler + library you have already installed, but your
> obviously missing the testsuite, because you didn't build it yourself. Now, you
> are on your own, because I have no idea how and where to fetch only the
> testsuite of the specific GCC you are running on the specific Linux you are
> running, and then adjust everything to run it with your already installed
> compiler, this is not the normal way we do those tests.
> 
> To repeat, the point was checking that your Linux and your hardware are sane,
> because I told you already that we know **for sure** that on current (and no so
> current) machines and Ubuntu, OpenSUSE, Fedora, whatever, that snippet works
> perfectly fine and *much* more than it, a whole testsuite.
> 
> So, it's up to you, I'll keep this open: if over the nest month or so you
> provide the testresults you get for either your specific GCC, current
> 4_4-branch, or current mainline on your OS + hardware, we can hope to make
> progress on your issue, otherwise nobody will commit suicide, and the issue
> will be simply closed for lack of meaningful feedback from submitter.

It's ok man, no offense here. I really didn't want to stomp on any feet.

All I'm trying to do is to figure out why I'm having this problem and how to
fix it. Abusing this bug tracker for a little conversation was a pleasure to
me, getting you upset wasn't my intention. My apologies for that.

So I will just do as you say and try to fix my distribution (or bug it's
maintainers) instead of getting into your way. Anyway, thanks a lot for your
help so far.


-- 


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


  parent reply	other threads:[~2010-01-16  1:08 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 20:21 [Bug libstdc++/42734] New: " phil at nwl dot cc
2010-01-13 20:22 ` [Bug libstdc++/42734] " phil at nwl dot cc
2010-01-13 20:23 ` phil at nwl dot cc
2010-01-13 20:24 ` phil at nwl dot cc
2010-01-13 20:41 ` paolo dot carlini at oracle dot com
2010-01-13 21:33 ` redi at gcc dot gnu dot org
2010-01-13 21:37 ` redi at gcc dot gnu dot org
2010-01-13 22:34 ` phil at nwl dot cc
2010-01-13 22:37 ` phil at nwl dot cc
2010-01-13 22:40 ` paolo dot carlini at oracle dot com
2010-01-13 22:40 ` paolo dot carlini at oracle dot com
2010-01-13 22:53 ` phil at nwl dot cc
2010-01-13 23:10 ` paolo dot carlini at oracle dot com
2010-01-13 23:34 ` redi at gcc dot gnu dot org
2010-01-14  1:14 ` phil at nwl dot cc
2010-01-14  1:59 ` paolo dot carlini at oracle dot com
2010-01-14 21:36 ` paolo dot carlini at oracle dot com
2010-01-15  1:49 ` phil at nwl dot cc
2010-01-15  1:55 ` phil at nwl dot cc
2010-01-15  2:00 ` paolo dot carlini at oracle dot com
2010-01-15  2:02 ` paolo dot carlini at oracle dot com
2010-01-15  2:05 ` paolo dot carlini at oracle dot com
2010-01-15 22:07 ` phil at nwl dot cc
2010-01-15 22:15 ` paolo dot carlini at oracle dot com
2010-01-15 22:32 ` phil at nwl dot cc
2010-01-15 23:07 ` paolo dot carlini at oracle dot com
2010-01-15 23:49 ` phil at nwl dot cc
2010-01-16  0:05 ` paolo dot carlini at oracle dot com
2010-01-16  1:08 ` phil at nwl dot cc [this message]
2010-01-16 10:10 ` paolo dot carlini at oracle dot com
     [not found] <bug-42734-4@http.gcc.gnu.org/bugzilla/>
2010-10-15 18:46 ` nacitar at gmail dot com
2010-10-15 18:49 ` pinskia at gcc dot gnu.org
2010-10-15 19:28 ` redi at gcc dot gnu.org
2010-10-15 19:38 ` redi at gcc dot gnu.org
2010-10-15 19:45 ` redi at gcc dot gnu.org
2010-10-15 19:47 ` nacitar at gmail dot com
2010-10-15 20:07 ` redi at gcc dot gnu.org
2010-10-15 23:42 ` paolo.carlini at oracle dot com
2010-10-16 13:32 ` redi at gcc dot gnu.org
2010-10-16 15:54 ` redi at gcc dot gnu.org
2010-10-17  9:57 ` paolo.carlini at oracle dot com
2014-07-18  5:43 ` damien.buhl at lecbna dot org
2014-12-03 18:40 ` fenixk19 at mail dot ru
2014-12-04 12:52 ` fenixk19 at mail dot ru
2014-12-04 12:55 ` damien.buhl at lecbna dot org
2014-12-04 19:28 ` fenixk19 at mail dot ru
2014-12-05  0:26 ` damien.buhl at lecbna dot org
2014-12-08 15:54 ` damien.buhl at lecbna dot org
2014-12-08 21:05 ` fenixk19 at mail dot ru
2015-10-05 10:18 ` redi at gcc dot gnu.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=20100116010803.2080.qmail@sourceware.org \
    --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).