Dalibor Topic wrote: >Ito Kazumitsu wrote: >> Sorry for missing your message. I did not think that would be a >> problem to me. > >Same here ;(
It's ok. Even I did not have confidence whether this bug is only for *BSD, or more general. Whenever I found a bug for a port, I compare it with RH8.0 or FC3, and this time generating info files are ok on RH8.0 and I guess it should be *BSD specific. I then have to check why I and Kaz have different result on RH8.0. >Sounds fine to me. Do the info files get built during a make dist step? >Then we could simply add a "make dist classpath" step to the resync >script, and untar that over the classpath dir, instead of copying the >files over. ... >In general, GNU Classpath tries to keep generated files out of its CVS, >so no configure scripts, Makefile.in files, and I guess no info files >either. It's a different phiolosophy. ;) > >That's why the resync-classpath script does an autogen.sh call on the >newly checked out GNU Classpath. Then, I'd like not to simply put info files into CVS, and try to find better solution. I think Classpath's people's philosophy is practical from the point of consistency. Kiyo _______________________________________________ kaffe mailing list kaffe@kaffe.org http://kaffe.org/cgi-bin/mailman/listinfo/kaffe