Closed Bug 5189 Opened 25 years ago Closed 25 years ago

BSDI /bin/sh handles "." differently, prevents configure running

Categories

(SeaMonkey :: Build Config, defect, P3)

x86
BSDI
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jepler, Assigned: slamm)

Details

I'm trying to build M4 on bsdi2.1. I get the following error: -> ./configure .: Can't open load-mozconfig.sh this is because /bin/sh on bsdi2.1 does not search $PATH for the file argument to ".". The following change seems to fix it, and I believe but am unsure that it will continue to function properly on shells which do search $PATH for ".": --- altoptions.m4.orig Fri Apr 16 12:48:34 1999 +++ altoptions.m4 Fri Apr 16 12:50:27 1999 @@ -98,7 +98,7 @@ # See the load-mozconfig.sh script for more details. TOPSRCDIR=`dirname [$]0` PATH="$TOPSRCDIR/build/autoconf:$PATH" -. load-mozconfig.sh]) +. $TOPSRCDIR/load-mozconfig.sh]) dnl This gets inserted at the top of the configure script MOZ_READ_MOZCONFIG
Rather, . $TOPSRCDIR/build/autoconf/load-mozconfig.sh
Assignee: ramiro → slamm
I added this. I'll take a look.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Ok, I checked in the fix. I am not sure if configure will pick up this change automatically (i.e. The cron job may only have a dependency on configure.in). I changed these files, mozilla/build/autoconf/load-mozconfig.sh mozilla/build/autoconf/altoptions.m4
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.