Am Sonntag, 29. Februar 2004 05:11 schrieb Grzegorz B. Prokopski: > Hi! > > Thanks to help from Bdale the problem seems to boil down to using "o" > option in 'tar chof' which turns on old, v7 mode, which doesn't allow > for paths longer than 100 chars. Old tar worked because it forced > usage of POSIX tar settings even when asked otherwise (it was a bug). > > $ grep -R chof . > ./Makefile: $(AMTAR) chof - $(distdir) | GZIP=$(GZIP_ENV) gzip -c > > >$(distdir).tar.gz > > ./Makefile: $(AMTAR) chof - $(distdir) | GZIP=$(GZIP_ENV) gzip -c > > >$(distdir).tar.gz > > ./Makefile.in: $(AMTAR) chof - $(distdir) | GZIP=$(GZIP_ENV) gzip -c > > >$(distdir).tar.gz > > ./Makefile.in: $(AMTAR) chof - $(distdir) | GZIP=$(GZIP_ENV) gzip -c > > >$(distdir).tar.gz > > So this options seems to come from automake as it's not present in > Makefile.am, but put into Makefile.in. Is there some way to persuade > automake not to enforce old compatibility mode when using tar?
Thanks for debugging this. What versions of automake have you tried ? Perhaps we should get more restrict on the version. Have you considered writting a bug report agains automake ? Michael _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
