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?
HTH
Grzegorz B. Prokopski
PS: The test case is ex. this:
cd /tmp
mkdir -p
sablevm-classpath-1.1.0/external/jaxp/source/javax/xml/transform
echo "AAAAAA"
>./sablevm-classpath-1.1.0/external/jaxp/source/javax/xml/transform/TransformerConfigurationException.java
tar chof - sablevm-classpath-1.1.0 | GZIP=--best gzip -c
>sablevm-classpath-1.1.0.tar.gz
tar zxvf ./sablevm-classpath-1.1.0.tar.gz
If you s/chof/chf/ - it works as expected.
--
Grzegorz B. Prokopski <[EMAIL PROTECTED]>
Debian GNU/Linux http://www.debian.org
SableVM - LGPLed JVM http://www.sablevm.org
Why SableVM ?!? http://devel.sablevm.org/wiki/WhySableVM
_______________________________________________
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath
