[gambit-list] OSX - 4.6.4 prebuilt images installation shows failure

Marc Feeley feeley at iro.umontreal.ca
Wed Feb 15 21:13:41 EST 2012


On 2012-02-15, at 9:44 AM, Sid H wrote:

> 
> On 15-Feb-2012, at 7:52 PM, Marc Feeley wrote:
> 
>> 
>> On 2012-02-15, at 9:14 AM, Sid H wrote:
>> 
>>> Hi all,
>>> 
>>> I tried the prebuilt macosx images, but they both show failures when installing. I downloaded the dmg files from http://www.iro.umontreal.ca/~gambit/download/gambit/v4.6/prebuilt/gambc-v4_6_4-macosx-intel32.dmg and http://www.iro.umontreal.ca/~gambit/download/gambit/v4.6/prebuilt/gambc-v4_6_4-macosx-intel64.dmg 
>>> 
>>> The final summary say "The installation failed. The installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
>>> 
>>>> From a terminal I'm able to run gsi and gsc after this. I presume its because I don't have gcc installed (yet!). Is that a possible reason? Does the installer try to run something that requires gcc?
>>> 
>>> I'm on a new Macbook Pro (hence no gcc), and I tried both the 32bit and 64bit versions.
>> 
>> That is strange.  I have used the 32 bit installer to install v4.6.4 on a MacBook pro (early 2011 version), a 3 year old MacBook Pro, a 2 year old iMac, and there were no issues.
>> 
>> Have you checked some obvious things (perhaps your disk is full, or your download was corrupted (which browser did you use?)).
> 
> There's plenty of space on disk; gambit-c is one of the first things I'm installing. To download I used Safari. Are the MD5 checksums available? I have the following 
> 
> $ md5 gambc-v4_v4_6_4-macosx-intel*
> MD5 (gambc-v4_6_4-macosx-intel32.dmg) = f48c3f366762045a1d032e35f5610c93
> MD5 (gambc-v4_6_4-macosx-intel64.dmg) = 6ab0a9d71baeee026629c8b9fe6ce7be

It seems you have the right files.  Here are the MD5 sums:

258c3b689248ea000f86f94284509f3d  gambc-v4_6_0-macosx-G3.dmg
39cc34b6e66bd67dfe9a4fb36a0164b1  gambc-v4_6_0-macosx-G4.dmg
c07c8e5736b450fa3aecf1b25eb03755  gambc-v4_6_0-macosx-G5.dmg
d5956448e8b3beb932e5c705a8f02a0e  gambc-v4_6_0-macosx-intel32.dmg
90d70ce6daeb8ffe650e0a4bfb6c0b58  gambc-v4_6_0-macosx-intel64.dmg
ba359706c61fc9853a4a85367c44f105  gambc-v4_6_0-macosx-universal.dmg
63546c6adbb26a2d35d1d664d8654d34  gambc-v4_6_0-windows-mingw.exe
7c8510c942afc13323488e7cbd5f04aa  gambc-v4_6_0-windows-visualc.exe
205d800a8c6ea3fe8637646ee5b8c297  gambc-v4_6_1-macosx-intel32.dmg
4fbb2dedf711ed98d555e963d8d4e4e6  gambc-v4_6_1-macosx-intel64.dmg
7ec78448d09786c6725924b9d4189b49  gambc-v4_6_1-windows-mingw.exe
3f5e268226477859753c6a898eccccc8  gambc-v4_6_1-windows-visualc.exe
7da1eca291360bf549245bc10e96c89d  gambc-v4_6_2-macosx-intel32.dmg
69557d88f0cf57b883e37ecbdbe09dc7  gambc-v4_6_2-macosx-intel64.dmg
610167c3e383f2e2194673319868673c  gambc-v4_6_2-windows-mingw.exe
23ab8a9c4ef5b484673b5c7c7e142111  gambc-v4_6_2-windows-visualc.exe
58f522d2014ea1040ef99f3660fa7ccb  gambc-v4_6_3-macosx-intel32.dmg
c0b484a288e353d8d9196480b0579192  gambc-v4_6_3-macosx-intel64.dmg
a9c61e1bd852d44fb25a0dd80773ced2  gambc-v4_6_3-windows-mingw.exe
7f17897c830f6506c724f0ce912a051e  gambc-v4_6_3-windows-visualc.exe
f48c3f366762045a1d032e35f5610c93  gambc-v4_6_4-macosx-intel32.dmg
6ab0a9d71baeee026629c8b9fe6ce7be  gambc-v4_6_4-macosx-intel64.dmg
7dd767feae9623042d0bffd045537427  gambc-v4_6_4-windows-mingw.exe
9c6fc0236a3a70378376e2de60012a89  gambc-v4_6_4-windows-visualc.exe

> 
>> 
>> I wonder if the precise error message was added to the system log.  Can you check the content of /var/log/system.log ?
> The log has the following - 
> 
> Feb 15 19:47:23 h83-5 installd[2346]: Starting
> Feb 15 19:47:23 h83-5 installd[2346]: uid=0, euid=0
> Feb 15 19:47:26 h83-5 Installer[2340]: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
> Feb 15 19:47:33 h83-5 installd[2346]: Exiting.

That's not very useful!  I have no clue what is happening.  I'm copying below the file InstallationCheck.in, from which the file InstallationCheck is generated by the configure script.  This file is used by the installer to make sure that installing Gambit will not clobber any existing file.  Normally, when this happens the installer will display a message, so I don't think this is the problem.  But please have a look at the file in case something catches your eye.

Marc


#! /bin/sh

# Copyright (c) 1994-2009 by Marc Feeley, All Rights Reserved.

PROGRAMS="@PROGRAMS@"
LIBRARIES="@LIBRARIES@"
INCLUDES="@INCLUDES@"

BIN_DIR="@BIN_DIR@"
LIB_DIR="@LIB_DIR@"
INCLUDE_DIR="@INCLUDE_DIR@"

INSTALL_DIR="@INSTALL_DIR@"
GAMBC_BIN_DIR="$INSTALL_DIR/current/bin"
GAMBC_LIB_DIR="$INSTALL_DIR/current/lib"
GAMBC_INCLUDE_DIR="$INSTALL_DIR/current/include"

FIRST_EXISTING_INCORRECT=""

i=0

check_clobber() # dir, gambc_dir, files
{
  DIR="$1"
  GAMBC_DIR="$2"
  FILES="$3"

  EXISTING_CORRECT=""
  EXISTING_INCORRECT=""
  MISSING=""

  if [ "$FIRST_EXISTING_INCORRECT" == "" ] ; then

    for f in $FILES ; do

      if [ -e "$DIR/$f" ] ; then
        if [ -L "$DIR/$f" -a "`readlink \"$DIR/$f\"`" == "$GAMBC_DIR/$f" ] ; then
          EXISTING_CORRECT="$EXISTING_CORRECT $f"
        else
          EXISTING_INCORRECT="$EXISTING_INCORRECT $f"
          if [ "$FIRST_EXISTING_INCORRECT" == "" ] ; then
            FIRST_EXISTING_INCORRECT="$i"
          fi
        fi
      else
        MISSING="$MISSING $f"
      fi

      i=`expr $i + 1`

    done

    if [ "$FIRST_EXISTING_INCORRECT" != "" ] ; then
      for f in $EXISTING_INCORRECT ; do
        echo "The installation process is being aborted because the file $DIR/$f exists and it was not created by the Gambit-C installer."
      done
      exit `expr $FIRST_EXISTING_INCORRECT + 16 + 96`
    fi

    echo "EXISTING_CORRECT   = $EXISTING_CORRECT"
    echo "EXISTING_INCORRECT = $EXISTING_INCORRECT"
    echo "MISSING            = $MISSING"
  fi
}

check_clobber "$BIN_DIR" "$GAMBC_BIN_DIR" "$PROGRAMS"
check_clobber "$LIB_DIR" "$GAMBC_LIB_DIR" "$LIBRARIES"
check_clobber "$INCLUDE_DIR" "$GAMBC_INCLUDE_DIR" "$INCLUDES"

exit 0




More information about the Gambit-list mailing list