I know I'm late with the answer, but a very quick and zero setup solution is to have a separate terminal window with:
sudo fs_usage | grep javac (fs_usage must be run as a superuser) Attila. On 2009.04.23., at 2:02, John Rose wrote: > > On Apr 22, 2009, at 4:43 PM, hlovatt wrote: > >> Hi Ben, >> >> I get exactly the same result with your build: > > It's a pain when the tools won't listen to your intended > configuration. > > One way to investigate (that sometimes helps me) is to look underneath > the tools to see what pathnames they are accessing. On Solaris it is > "truss", on older Macs it is "ktrace", and on Leopard it is "dtrace". > It requires a very modest "sudo" setup. Here's an article on dtrace: > > http://www.macosxhints.com/article.php?story=20071031121823710 > > I have no idea why this should be necessary, but you could try to > force your explicit rt.jar earlier into javac's search order: > > javac -Xbootclasspath/p:$myjrelib/rt.jar ... > > -- John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to jvm-languages@googlegroups.com To unsubscribe from this group, send email to jvm-languages+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
