OK, I'm not actually certain that either linux emulation _or_ amd is the
culprit here, but *something* is definitely going on, and at the moment 
I don't have an easy way to eliminate linux emulation as a factor.

I've been playing around with Java lately (no jeers, please :), 
on an i386 box, and the JDK I'm using (from pkgsrc, sun-jdk14) runs
under Linux emulation.   I have two main boxes I work from - one
slowish one with a lot of disk, and a faster workstation that I
use as a desktop and automount some things (including my home directory
and pkgsrc tree) from the slower box.  Both machines are running the
same OS - 1.6ZG as of mid-December or so.

The _first_ thing I noticed is that I can build pkgsrc/devel/apache-ant
on the slower, non-automounting box just fine, but on my desktop,
it blows up:

===> Building for apache-ant-1.5.4
... Bootstrapping Ant Distribution
... Compiling Ant Classes
src/main/org/apache/tools/ant/Project.java:71: cannot resolve symbol
symbol  : class DefaultInputHandler 
location: package input
import org.apache.tools.ant.input.DefaultInputHandler;
                                  ^
src/main/org/apache/tools/ant/Project.java:72: cannot resolve symbol
symbol  : class InputHandler 
location: package input
import org.apache.tools.ant.input.InputHandler;
                                  ^
[lots of errors deleted]

Not really knowing enough to troubleshoot this, I punted and installed
a binary package of ant from the slower machine.

Next, I tried compiling the example source code from Bruce Eckel's
"Thinking in Java" in my home directory.  Once again, this works
fine from the slower machine, but not from the faster one - it seems
unable to properly resolve stuff on the CLASSPATH.

Trying to figure out what the difference might be, I wondered
if the symlinks generated by amd might be causing confusion, so
I moved the example code to a local directory on the faster machine,
and it built cleanly!  However, code on a straight NFS mount (no AMD)
didn't build either, so I don't know that that amd has anything to
do with it.

Does anyone know what's going on here?  Any suggestions for what to
look at next for troubleshooting?   Should I have sent this to
a different list?

Thanks in advance,
+j

-- 
Jeff Rizzo                                         http://boogers.sf.ca.us/~riz