public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "karx11erx at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug c++/36576] gcc 4.3.1 doesn't build for me on openSUSE 10.3 Date: Fri, 20 Jun 2008 11:00:00 -0000 [thread overview] Message-ID: <20080620110009.9469.qmail@sourceware.org> (raw) In-Reply-To: <bug-36576-16337@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from karx11erx at hotmail dot com 2008-06-20 11:00 ------- (In reply to comment #5) > (In reply to comment #3) > > Update your system. Report this bug to OpenSUSE. > > > > *** This bug has been marked as a duplicate of 35257 *** > > > > I have been searching around a little and found that the gjar used by openSUSE > 10.3 belongs to a classpath package that is coming from gnu.org > (http://www.gnu.org/software/classpath/). Seems pretty daft to me to claim this > would be a bug I'd have to report to SUSE. > (In reply to comment #3) > Update your system. Report this bug to OpenSUSE. > > *** This bug has been marked as a duplicate of 35257 *** > Now this is great: I have found the latest classpath source, but: I have no clue where to have install put the stuff in - though that doesn't matter, because the install procedure needs several libraries in newer versions than I have installed on my system, and which do not seem to be available from SUSE. So I can either try to collect all that stuff from somewhere from the internet and install it manually, hoping it doesn't break my system, spending hours and hours of additional work with dubious prospect of success, or wait for SUSE to release gcc 4.3. All that because some not so smart people chose classpath over Sun's java libs for the sake of it being free, although it is not yet available in a version that indicates it would be stable, and that is at least 1.something. And all that is why? Because gcc 4.1 throws some errors on our code that works flawlessly with MS compilers and gcc 3, and that absolutely do not seem to be justified, and I wanted to make sure this problem is either fixed or still present in the latest gcc release in order to avoid remarks like "update to the latest compiler version". I would so love to use Linux, but as soon as you leave the beaten path of common distros and are not an expert of sorts, you are completely lost with this operating "system" (I miss the "system" in this stuff). When will you Linux geeks learn to get your act together, if you ever want to offer a true alternative to Windows? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36576
next prev parent reply other threads:[~2008-06-20 11:00 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-36576-16337@http.gcc.gnu.org/bugzilla/> 2008-06-19 12:10 ` pinskia at gcc dot gnu dot org 2008-06-19 15:59 ` karx11erx at hotmail dot com 2008-06-19 16:02 ` pinskia at gcc dot gnu dot org 2008-06-19 20:01 ` karx11erx at hotmail dot com 2008-06-20 9:58 ` karx11erx at hotmail dot com 2008-06-20 11:00 ` karx11erx at hotmail dot com [this message] 2008-06-20 11:02 ` pinskia at gcc dot gnu dot org 2008-06-20 11:04 ` pinskia at gcc dot gnu dot org 2008-06-20 12:28 ` karx11erx at hotmail dot com 2008-06-20 12:33 ` karx11erx at hotmail dot com 2008-06-20 12:37 ` pinskia at gcc dot gnu dot org 2008-06-20 13:03 ` karx11erx at hotmail dot com 2008-06-20 14:01 ` pinskia at gcc dot gnu dot org 2008-06-21 8:57 ` karx11erx at hotmail dot com
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=20080620110009.9469.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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).