This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Problem building gcc-2.95.2 under SCO 2.1.1
- To: scherrey at proteus-tech dot com
- Subject: Re: Problem building gcc-2.95.2 under SCO 2.1.1
- From: Robert Lipe <robertlipe at usa dot net>
- Date: Tue, 30 Nov 1999 15:20:59 -0600
- Cc: gcc <gcc at gcc dot gnu dot org>
- References: <38442B41.CDB65D5F@switchco.com>
Benjamin Scherrey wrote:
> Well after getting a pretty good ways into the build (and several
> hours later - slow computer), during stage1 I get the following error:
>
> Undefined symbol First referenced in
> alloca genattr.o
>
> I'm only using the SCO compiler and gcc-2.95.2 source code.
I don't have ready access to a UW2 system, but 2.95.2 worked for me
on UW7 which I believe to be equivalent in all pertinent ways.
[ pause ]
I just kicked off a your configure line below on UW7.1.0 with GNU make
and SCO /bin/cc and was unable to duplicate it. (full three-stage in 17
minutes. Nice.)
The alloca thing is often caused by mixing and matching compilers; if
you configured with GCC but built with /bin/cc, you'll get behaviour
like this. Is it possible that you've crossed the streams at some
point? Did you have CC in your environment during the configure?
Did you do a 'make bootstrap' or a 'make'?
Was this during the build of stage1 or during the build with stage1/?
(Please include more context in your report.)
> Will building binutils on this box first solve this problem?
No.
> My configure command was: ./configure --enable-shared --prefix=/usr
> --exec-prefix=/usr
Ick. You have no right to complain if a 'make install' nukes your
system files...
> config.guess returned: i386-pc-sysv4.2uw2.1.1
>
> Also, configure failed if I tried to do it from another directory so I
None of SCO's makes are up to the "source in one place, object in
another" that works so well with the GNU projects. I highly recommend
using GNU make. It's available on www.sco.com/skunkware if you don't
want to build it.
RJL