AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2006.03.27 23:18 "[Tiff] Compile errors Tiff-3.8.0 on FreeBSD 5.4", by Karyn Williams
2006.03.28 00:16 "Re: [Tiff] Compile errors Tiff-3.8.0 on FreeBSD 5.4", by Bob Friesenhahn
2006.03.28 06:19 "Re: [Tiff] Compile errors Tiff-3.8.0 on FreeBSD 5.4", by Kai-Uwe Behrmann
2006.03.31 16:30 "[Tiff] configure in tiff-3.8.2 cannot deal with path with spaces", by
2006.03.31 17:38 "Re: [Tiff] configure in tiff-3.8.2 cannot deal with path with spaces", by Bob Friesenhahn
2006.04.03 09:23 "Re: [Tiff] configure in tiff-3.8.2 cannot deal with path with spaces", by
2006.04.03 14:33 "Re: [Tiff] configure in tiff-3.8.2 cannot deal with path with spaces", by Bob Friesenhahn
2006.04.03 17:02 "Re: [Tiff] configure in tiff-3.8.2 cannot deal with path with spaces", by

2006.04.03 17:02 "Re: [Tiff] configure in tiff-3.8.2 cannot deal with path with spaces", by

If this is an autoconf's bug, should I file a bug against it? I cannot believe that in the twenty-first century we cannot yet deal with spaces and other characters in the pathname…

Autoconf produces a Unix shell script. Unix shell scripts pass arguments to sub-commands using spaces to delimit the arguments. Sometimes argument lists are expanded multiple times and expanded arguments may include spaces. Given the differences in shell behavior across the many systems that Autoconf supports, it is a very difficult job to fix the spaces problem. The Autoconf maintainers are well aware of the issue but no fix is within easy reach.

Thanks for the thoroughly explanation, Bob.

I'll study shell scripting and autoconf, maybe I'll come up with a patch only for my particular system.

In the meantime, I'll try to get rid of spaces in the path. Regards,

--
Andrea "XFox" Govoni

AIM/iChat/ICQ: xfox@mac.com
Yahoo! ID: xfox82
Skype Name: draykan

PGP
KeyID: 0x212E69C1
Fingerprint: FBE1 CA7D 34BE 4A53 9639 5C36 B7A0 605F 212E 69C1