This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: OSR5.02 and whoops solved (?)


> The problem I am having with OSR 5.0.2 getting va_list defined wrongly seems
> to be due to the existence of an _old_ gcc 2.7.2.1 on the system I am
> making egcs on.  That gcc has a varargs.h file that is being
> picked up by the top level "make bootstrap".  The top level "make bootstrap"
> is using that old gcc as the native compiler.

Yes, I've been looking at your system {as you requested} this morning.

The gcc you have on this system does not support this system.


$ uname -X | grep Rel
Release = 3.2v5.0.2
$ gcc -v /tmp/x.c
Reading specs from /usr/local/lib/gcc-lib/i486-unknown-sco3.2v4.2/2.7.2.1/specs
gcc version 2.7.2.1

[ Many other clues that this is a 3.2v4 targeted gcc that was 
**almost** hacked to run on OpenServer 5 (a.k.a. 3.2v5).

What you're seeing is one of the many many things between "almost 
ported" and "ported".

In fact, this is covered in the FAQ for c.u.s.p.

	http://www.dgii.com/cgi-bin/scoprgfaq/faq.pl?file=6

with some additional information at:
	
	ftp://ftp.dgii.com/users/robertl/scods/gds_faq.html


If you knew how broken it was, you'd be afraid.  Very afraid.

> 	I've got a _lot_ of folks depending on the gcc 2.7.2.1 compiler
> to incorrectly compile a large software project, so I can't just remove
> it right now.  That would be the simplest solution by far.

Simpler yet:

CC=path to workign compiler configure
CC=path to working compiler make bootstrap

More specifically:

CC="/bin/cc -belf" configure
CC="/bin/cc -belf" make bootstrap

Enjoy.

RJL


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]