🚀 go-pugleaf

I am trying to install gcc v2.7.0 on our system here because of a bug
I noticed in the installed v2.5.8.  Here is a program that exhibits
the bug:

------ begin bugtest.c ------

#include<stdio.h>
#include<limits.h>

main()
{
  if( INT_MIN > INT_MAX )
    printf("I'm buggy.\n");
  else
    printf("I'm clean.\n");

  return 0 ;
}

------  end bugtest.c  ------

The installed gcc v2.5.8 prints `I'm buggy'.  Now, here's the deal.  I
have followed the gcc compilation instructions in order to build the
new version on our Sparc 10/SunOS 4.1.4 system.  I have built stage2
and stage3 for c, c++, and objective c.  Now, if I am in the gcc main
src directory and type

  ./stageN/xgcc -BstageN/ -o bugtest bugtest.c

for N=2 or N=3, I get the result, `I'm clean'.  However, as soon as I
do the install of either stage2 or stage3 and then do a normal

  gcc -o bugtest bugtest.c

I get the buggy result again.  What is the difference between the
compiled binaries sitting in the source directories and the programs
which get installed?  Why is the exact same executable turning up
buggy in one case but not in the other?  I'm really getting frustrated
on this one.  Please, if you have any suggestions, send them (carbons
to e-mail would be appreciated).

CJW

--
**********************************************************************
    /\       Colin J. Wynne             Johns Hopkins University
   (())                              Dep't of Mathematical Sciences
  /____\   ``Lunatic-at-Large''    E-Mail:  cwynne@brutus.mts.jhu.edu
 /______\   
/________\  Q: What do you call a short psychic who escapes
               from prison?
            A: A small medium at large.
**********************************************************************