Hi Victor, On Wed, 20 Aug 2003 16:17:34 -0400, Victor Eijkhout wrote: > checking for ranlib... ranlib > checking for powerpc-apple-darwin6.6-windres... no > checking for windres... windres > checking whether to enable maintainer-specific portions of Makefiles... no > updating cache ./config.cache > creating ./config.status > creating Makefile > Configuring in libiberty > /Volumes/TiBook: /Volumes/TiBook: No such file or directory > make: *** [configure-libiberty] Error 1 > > The problem here is that that directory is "/Volumes/TiBook\ > Hard\ Drive". In other words, some configure script should double > quote the environment variable $HOME. > > Is this a problem for the fvwm2 maintainer?
First of all sorry that I am not the maintainer but this is a gerneral error that affects all maintainers since it is not common in unixlike Operatingsystems to use spaces in pathnames since this is in relation is a new feature and I can remember that my first expierence with spaces in filenames was with a Windwos 98 Machine up to this time spaces where quite uncommen in my Atari and DOS World, in facht files crashed or didn't get save when there were spaces in the name or in the path. Don't know how it was with Classic OSes or other unixlike Operatingsystems. So in order to have a smooth running Mac OS X you should avoid using spaces in pathnames. I also had to remember about this as well but now I am used to it and even under Windows it is now quite more easy to navigate via commandline when you have _ or - in path and file name instead of a blank space mark. Eric Hoch ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ Fink-beginners mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-beginners
