RE: Error in compilation of GCC 3.0.3

["Dana, Eric" <Eric_Dana at bmc dot com>]

Janis,

   I've made patches for Gcc 3.0.3 that will work on Dynix 4.4.2-4.6.1.
   I will post them shortly.

Eric Dana
BMC Software Inc.

-----Original Message-----
From: Janis Johnson [mailto:janis187@us.ibm.com]
Sent: Thursday, February 07, 2002 7:59 PM
To: Johan van den Berg
Cc: gcc@gnu.org
Subject: Re: Error in compilation of GCC 3.0.3


On Thu, Feb 07, 2002 at 11:11:51AM +0200, Johan van den Berg wrote:
> Here is my story:
>
> OS: i386-sequent-sysv4

Which version of DYNIX/ptx are you running?  I played with GCC on ptx
over a year ago and found that there are different problems that crop
up on each version.  I didn't have the time to track them all down and
don't now, either, but I might be able to help out some; I know more
about GCC now than I did at that time and I've got access to systems
running DYNIX/ptx V4.6.1, V4.5.3, and V4.4.7.

>
> I compiled and installed the following:
>  * GNU make 3.79
>  * GNU sed 3.02
>  * GNU bison 1.32
>  * flex 2.5.4a
>  * GNU binutils 2.11.2
>
> I renamed /usr/local/bin/as to /usr/local/bin/gas (gcc expects sequent as)
> I also renamed /usr/local/i386-sequent-sysv4/bin/as
>
> I built and installed gcc-2.8.1 under /opt/gcc-2.8.1.
> I set the path to /opt/gcc-2.8.1:/usr/local/bin:/usr/bin:/bin:.

I have GCC 2.95.3 on DYNIX/ptx but don't know if I can reproduce that
build.

> I extracted the source for gcc-3.0.3, and created a native obj directory:
> /home/vdberj/gcc-3.0.3/obj-sequent.

The installation instructions say that building where objdir is a
subdirectory of srcdir is unsupported; I ususally make them siblings.
That's not the problem here but could avoid other problems later in the
build.

> In that directory, I ran:
>   ../configure --with-gnu-ld --enable-languages=c,c++
>   make -j 3 bootstrap (or) make bootstrap (both fail)

If you're using GNU as, you need to pass --with-gnu-as to configure.

> Then, after about 30min of compiling, I get this:
>
> cc -DIN_LIBGCC1 -O -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/config
-I../../gcc/../include -DL_mulsi3 -c ../../gcc/libgcc1.c -o libgcc/_mulsi3.o
> "../../gcc/machmode.h", line 124: syntax error, probably missing ",", ";"
or "="
> "../../gcc/machmode.h", line 124: syntax error before or at: PARAMS
> "../../gcc/machmode.h", line 125: warning: syntax error:  empty
declaration
> "../../gcc/machmode.h", line 130: syntax error, probably missing ",", ";"
or "="
> "../../gcc/machmode.h", line 130: cannot recover from previous errors
> make[3]: *** [libgcc/_mulsi3.o] Error 1
> make[3]: Leaving directory `/home/vdberj/gcc/gcc-3.0.3/obj-sequent/gcc'
> make[2]: *** [libgcc.a] Error 2
> make[2]: Leaving directory `/home/vdberj/gcc/gcc-3.0.3/obj-sequent/gcc'
> make[1]: *** [stage1_build] Error 2
> make[1]: Leaving directory `/home/vdberj/gcc/gcc-3.0.3/obj-sequent/gcc'
> make: *** [bootstrap] Error 2
>
> Question: Do you know why this is hapening?
> Question: Why is it using cc, when using gcc-2.8.1 for the rest?
> Possibility: It seems as though my cc doesn't undestand PARAMS.

This particular problem can be avoided by adding -DIN_GCC to the
definition of CCLIBFLAGS in gcc/Makefile.in (although there's probably a
better way to do that).  This will let PARAMS be recognized.

A comment in gcc/Makefile.in says that the compiler used for libgcc1,
$OLDCC, should not be the GCC C compiler, so this is appropriate.

> Any help would be appreciated. Thank you beforehand.

I've been trying a bootstrap on a DYNIX/ptx 4.6 system today in my spare
cycles and keep running into additional problems, but I'm making
progress.  If you let me know which version of ptx you're using I'll try
my further trials on the same version.

> Johan van den Berg

Janis Johnson
former member of the Sequent compiler group
now in the IBM Linux Technology Center