tagging classpath for GCC import

[Andrew Hughes]

----- Original Message -----
> Am 02.12.2012 22:20, schrieb Mark Wielaard:
> > Hi,
> > 
> > Matthias wanted to import the latest classpath from git into libgcj
> > so I have pushed a tag (libgcj-import-20121202) for current HEAD.
> > (Note for future reference, to push a tag one uses git push --tags,
> > with just git push the tag stays local.)
> > 
> > It seems the git import from CVS lost the old tags. Does anybody
> > know of a way to get them from the original CVS history into the
> > git repository?
> 
> I had a hard time getting any clue that the CVS repo was abandoned.
> Now finally
> found http://savannah.gnu.org/git/?group=classpath which is not that
> obvious
> when you start at classpath.org.
> 

Try reading the mailing list.  It's been discussed at length at the time
and there's been discussion of commits to it since.

> Further, it looks like classpath did bump the requirement on autoconf
> to 2.69,
> and didn't even bother to document that (m4/iconv.m4 requires macros
> only found
> in 2.69).  classpath itself pretends to require 2.63.
>
> GCC has 2.64, and won't change for the next release. Any hint how to
> handle this
> properly?
>

Classpath works with 2.63 on RHEL6.  That's why I lowered it.

What macros are you referring to?  iconv.m4 is dated 2002 in the header.
 
>   Matthias
> 
> 

-- 
Andrew :)

Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: 248BDC07 (https://keys.indymedia.org/)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F  8F91 3B96 A578 248B DC07