Andrew Pinski <[EMAIL PROTECTED]> writes: > Classpath issues should goto the classpath project and not to GCC.
The classpath project fixed that portability bug long ago. I just checked, and it was fixed in classpath 0.07, released in 2003. The classpath developers didn't have to do any special work to fix it. They simply used the then-latest libtool. Daniel Jacobowitz writes that the GCC team has been working (slowly) on blockers that prevent easy import from libtool. I hope that this work succeeds, and that it also succeeds to allow easy import from classpath. If that will take a while, though, then it would make sense to install the ltmain and libjava/classpath/ltmain.sh parts of the proposed patch, since the GCC project is in effect maintaining its own forks of obsolete versions of libtool and classpath in the meantime. _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
