------- 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
