> I just discovered that if I type in the dot command with the full path > name (shown above) dot gives the error seen. If I CD to the directory > and run dot against the filename (no path) it succeeds. So, seems that > it's a path name issue. I wonder if something has changed with dot > lately. I also wonder if I supply a DOS style path if it would work. > I'm running in a bash shell, BTW. > > Suggestions? > > Jon
I was able to run dot against my .dot files manually within the directory the dot files were located in. Seems that's a workaround while I try to figure out what settings to use to get it to work as it did before. Jon ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Doxygen-users mailing list Doxygen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/doxygen-users
