there are several places in configure.in (and in configure script generated from the former) where test(1) utility is used in a way which breaks POSIX compliant test(1). POSIX (http://www.opengroup.org/onlinepubs/007904975/utilities/test.html) requires test(1) to use single = for string comparisions yet celestia's configure.in uses ==, which results in breaks on systems which don't use bash(1) as a /bin/sh (e.g. *BSD or SVr4 systems).
here is the patch for 1.3.0 release: http://Xtrmntr.org/salo/celestia-1.3.0-configure.in.diff
not POSIX compliant test(1) usage in configure.in
-
- Developer
- Posts: 944
- Joined: 18.07.2002
- With us: 22 years 4 months
- Location: Lyon (France)
-
Topic authorsalo