On May 3 09:41, Fedin Pavel wrote: > Supplying prefix=/ to configure script causes it to lock up. It > doesn't output any single line, just freezes. Even Ctrl-C doesn't > help. > I know this is maybe unusual, but i really know why i want to do > it. And, in fact, this is a legitimate operation. So, i consider > this to be a bug.
Yes, that's a bug in autoconf. It doesn't fully respect POSIX pathname rules. What happens is that it simply attaches pathnames with a leading slash to the prefix, for instance: ac_site_file1=$prefix/share/config.site Now, if prefix is /usr, everything's ok: ac_site_file1=/usr/share/config.site but if prefix -s just /: ac_site_file1=//share/config.site Double slashes on Cygwin prefix a network path "//server/share", just as in the UNC name convention. This is valid per POSIX, see http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html 4.12 Pathname Resolution [...] A pathname consisting of a single <slash> shall resolve to the root directory of the process. [...] A pathname that begins with two successive <slash> characters may be interpreted in an implementation-defined manner, although more than two leading <slash> characters shall be treated as a single <slash> character. What you can try as a workaround is to use --prefix=''. It should have the expected result. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
