[cp-patches] tagging classpath for GCC import

2012-12-02 Thread 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

Re: [cp-patches] tagging classpath for GCC import

2012-12-02 Thread Matthias Klose
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

Re: [cp-patches] tagging classpath for GCC import

2012-12-02 Thread Matthias Klose
Am 03.12.2012 02:15, schrieb Matthias Klose: 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