public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bryce@gcc.gnu.org
To: David.Billinghurst@riotinto.com, bryce@gcc.gnu.org,
	gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org,
	mec@shout.net, nobody@gcc.gnu.org
Subject: Re: java/2388: Cannot compile libgcj on case insensitive file system?
Date: Tue, 23 Jul 2002 21:53:00 -0000	[thread overview]
Message-ID: <20020724045339.26417.qmail@sources.redhat.com> (raw)

Synopsis: Cannot compile libgcj on case insensitive file system?

Responsible-Changed-From-To: unassigned->bryce
Responsible-Changed-By: bryce
Responsible-Changed-When: Tue Jul 23 21:53:38 2002
Responsible-Changed-Why:
    .
State-Changed-From-To: open->closed
State-Changed-By: bryce
State-Changed-When: Tue Jul 23 21:53:38 2002
State-Changed-Why:
    Fixed in mainline and GCC 3.1.1 by:
    
    2002-05-18  Mark Mitchell  <mark@codesourcery.com>
    
    	* gjavah.c (throwable_p): Do not free the name of the class after
    	passing it to find_class.
    	* java-tree.h (CLASS_BEING_LAIDOUT): Remove duplicate definition.
    	* jcf-io.c (dirent.h): Include it.
    	(fnmatch.h): Likewise.
    	(compare_path): New function.
    	(java_or_class_file): Likewise.
    	(memoized_dirlist_entry): New type.
    	(memoized_dirlist_lookup_eq): New function.
    	(memoized_dirlists): New variable.
    	(caching_stat): New function.
    	(memoized_class_lookup_eq): New function.
    	(memoized_class_lookups): Likewise.
    	(find_class): Use memoized_class_lookups and caching_stat.
    	* jcf.h (JCF_USE_SCANDIR): Define.
    	* parse.y (java_expand_classes): Write the class files in reverse
    	order.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2388


                 reply	other threads:[~2002-07-24  4:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020724045339.26417.qmail@sources.redhat.com \
    --to=bryce@gcc.gnu.org \
    --cc=David.Billinghurst@riotinto.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    --cc=mec@shout.net \
    --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: 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).