This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Class already defined -- same file, same line

From: Bryce McKinlay <mckinlay at redhat dot com>
To: Starling <pubsynxj8jw at pacbell dot net>
Cc: java at gcc dot gnu dot org
Date: Mon, 30 Aug 2004 17:12:46 -0400
Subject: Re: Class already defined -- same file, same line
References: <87sma5u3d9.fsf@pacbell.net> <4132DB79.9060103@gmail.com> <87vff0u61k.fsf@gnu.org> <87fz649xmt.fsf@pacbell.net>

Starling wrote:

Ranjit Mathew <rmathew@gmail.com> writes:

This bug should be fixed now on the mainline. If you can, I would advise you to pull a CVS snapshot, compile it and use it.
Are you sure?  I've had some bad experiences with relying on CVS
before, one developer even saying, and I quote, "Its CVS its supossed
to be broken."  While I hardly think the GCC people are that bad, I'm
not really well versed enough in CVS... isn't there some sort of
"release version tag thingy" that I should specify for stuff that
won't break?

GCC_3_4_BRANCH is the stable 3.4 series. If this bug is still present in 3.4, a PR should be filed and we will try to fix it for the next 3.4.x release.

Bryce

References:
- Class already defined -- same file, same line
  - From: Starling
- Re: Class already defined -- same file, same line
  - From: Ranjit Mathew
- Re: Class already defined -- same file, same line
  - From: Casey Marshall
- Re: Class already defined -- same file, same line
  - From: Starling

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]