public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/38685] classmap.db is zero bytes long in 64 bit directory
Date: Thu, 01 Jan 2009 12:09:00 -0000	[thread overview]
Message-ID: <20090101120949.13816.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38685-13830@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from rob1weld at aol dot com  2009-01-01 12:09 -------
(In reply to comment #1)
> Can you try 4.3.2?

No, I don't have it, and next I was planning on build-testing the trunk.


The reason for reporting "so old a version" (_if_ that is the point you are
making "Can you try 4.3.2?") is that I am reporting what I am currently
compiling. 

I am compiling 4.2.x because it is the newest version of gcc that has the
fewest number of "make -i check" errors while still being able to compile
the majority of the (poorly written) type of c++ source code that is still
available on the Internet. 

It (gcc 4.2.2) is the 'proverbial 3.4.3' of the 4.x series. Newer (but not
newest) gcc versions (like 4.3) cost (me) too much compatibility with the
old-c++ source still commonly available without adding enough incentive
(features, speed, compatibility, fewer compiler bugs).

When I get a 4.x series compiler installed (instead of my Operating System's
default 3.4.3 (from 2005)) I am going to work on the trunk.


> Can you try 4.3.2?
If there is a particular reason that we need 4.3.2 to work on OpenSolaris
and that you would prefer me to run the testsuites on 4.3.2 instead of
the trunk please let me know and I can set aside time to download / build /
check / and report it.

Rob


-- 

rob1weld at aol dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |major


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


  parent reply	other threads:[~2009-01-01 12:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-01  2:11 [Bug libgcj/38685] New: " rob1weld at aol dot com
2009-01-01  3:27 ` [Bug libgcj/38685] " pinskia at gcc dot gnu dot org
2009-01-01  9:14 ` schwab at suse dot de
2009-01-01 12:09 ` rob1weld at aol dot com [this message]
2009-01-01 12:40 ` rob1weld at aol dot com
2009-01-06  3:39 ` rob1weld at aol dot com
2009-01-19 17:09 ` rob1weld at aol dot com
2009-01-22 14:50 ` rob1weld at aol dot com
2009-02-13 15:55 ` rob1weld at aol dot com
2010-04-28 20:27 ` ro at gcc dot gnu dot 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=20090101120949.13816.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: 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).