Bug 4823 - test statements at end of configure script use non-portable ==
Summary: test statements at end of configure script use non-portable ==
Status: RESOLVED FIXED
Alias: None
Product: cairo
Classification: Unclassified
Component: general (show other bugs)
Version: 1.0.2
Hardware: PA-RISC (HP) HP-UX
: high normal
Assignee: Carl Worth
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
: 6087 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-10-20 04:44 UTC by Richard Lloyd
Modified: 2006-03-18 10:52 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Changes test statements to use portable shell syntax in configure.in (989 bytes, patch)
2005-12-08 06:02 UTC, Klaus Heinz
Details | Splinter Review

Description Richard Lloyd 2005-10-20 04:44:32 UTC
At the very end of the top-level configure script, there are a set of 6 test
statements that use "==" as a comparison. The /bin/sh shell in HP-UX 11.X
rejects this - it expects just one "=". It should be noted that all other test
statements in configure use the single "=". The configure.in script, of course,
has the same issue and is the file that will need fixing and then the configure
script re-generated from that.
Comment 1 Klaus Heinz 2005-12-08 06:02:09 UTC
Created attachment 4028 [details] [review]
Changes test statements to use portable shell syntax in configure.in

This also happens with pkgsrc (http://www.pkgsrc.org/) on NetBSD.
Comment 2 Carl Worth 2005-12-08 06:42:01 UTC
Thanks for the patch. This is now fixed in both cairo 1.1.1 and cairo 1.0.3
(those are both CVS-only versions, but the fix will appear in all subsequent
releases).


2005-12-07  Carl Worth  <cworth@cworth.org>

        * configure.in: Use more portable shell syntax, ('test =' rather
        than 'test =='). Thanks to Richard Lloyd and Klaus Heinz. Closes
        bug #4823.
Comment 3 Christian Biesinger 2006-03-19 05:52:58 UTC
*** Bug 6087 has been marked as a duplicate of this bug. ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.