>Number: 4372 >Category: config >Synopsis: Configure fails on Ultrix due to Bourne shell incompatibility >- easy fix >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri May 7 14:20:02 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.6 >Environment: Ultrix 4.4 on a DEC 5240 (MIPS) - C compiler irrelevant - doesn't get that far. >Description: Here's the output from configure without a trace :-
# ./configure --prefix=/usr/local/apache Configuring for Apache, Version 1.3.6 sh: --: bad option(s) If I trace execution, we see a trace which ends with :- [snip] + eval val=$EXTRA_CFLAGS val= + [ x != x ] + eval val=$EXTRA_LDFLAGS val= + [ x != x ] + eval val=$EXTRA_LIBS val= + [ x != x ] + eval val=$EXTRA_INCLUDES val= + [ x != x ] + eval val=$EXTRA_DEPS val= + [ x != x ] IFS= + [ x--prefix=/usr/local/apache = x ] + set -- --with-layout=Apache --prefix=/usr/local/apache sh: --: bad option(s) >How-To-Repeat: Just configure Apache 1.3.6 on Ultrix 4.4. >Fix: Yes - use the shell "sh5" rather than "sh". I have read in a Usenet posting that "Ultrix's sh is broken, and it is better to use the more 'historically accurate' alternative System V Bourne shell sh5 which DEC supply for this reason." If you do that, then configure runs OK (as far as I know). >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]
