>Number: 4820 >Category: config >Synopsis: ApacheJServ-1.0 configure breaks when run under hp's default >sh, sh-posix >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Aug 4 10:10:00 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.6 >Environment: HP-UX nimitz B.10.20 A 9000/859 1441553301 two-user license gcc --version 2.7.1 snapshot 951024 >Description: I'm building ApacheJServ-1.0 on HPUX 10.20 and ran into the following problem that seems to be due to /usr/bin/sh which is the POSIX.2-conformant command shell. The problem does not occur if I use /usr/old/bin/sh which is the "standard" Bourne shell.
Line 839 of configure missing_dir=`cd $ac_aux_dir && pwd` results in missing_dir=/usr/local/ApacheJServ-1.0/src/scripts/build/unix /usr/local/ApacheJServ-1.0/src/scripts/build/unix but should be missing_dir=/usr/local/ApacheJServ-1.0/src/scripts/build/unix This is because cd in the posix sh prints the path. If I change line 839 to missing_dir=`cd $ac_aux_dir > /dev/null 2>&1 && pwd` the problem is fixed. Alternatively I could put /usr/old/bin before /usr/bin in my path to get the old bourne shell. >How-To-Repeat: run configure on hpux 10.20 with /usr/bin in PATH ahead of /usr/old/bin >Fix: If I change line 839 of configure to missing_dir=`cd $ac_aux_dir > /dev/null 2>&1 && pwd` >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 make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database 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! ]
