Trouble untar-ing gcc, unknown filetype

[Steven Schweda · Accepted solution]

> Does this really mean I have to 1st build
> gcc v2.x 1st?

I'd say that it means that you need to build
just the (GCC) C compiler first. According
to:

http://gcc.gnu.org/install/configure.html

--enable-languages=lang1,lang2,...

where "lang1,lang2,..." is "c" (or something
like that).

In my last test, I did get it to go using
"CC=cc", and it did use "cc" for a while, but
I didn't save the log, and I can't be sure
that it didn't sneak in some premature use of
the available existing gcc (which I hadn't
discarded).

I mentioned my shell only in case the method
for setting the environment variable would
need to be different elsewhere. (Although I
find that bash has some nice features, so I'd
recommend it, I didn't mean to imply that it
was a requirement. Of course, you must be in
a download frenzy by now, so I should have
been more explicit about that.)

> bash-3.00# CC=cc ../gcc-3.4.6/configure
> -msg_disable=ptrmismatch,ptrmismatch1

That was supposed to be:
CC='cc -msg_disable=ptrmismatch,ptrmismatch1'
../gcc-3.4.6/configure

but the CFLAGS scheme is probably the
official one, anyway.

"3.00"? You and your old versions (again).


My Tru64 system is running VMS today, so I
may be (even) less help than usual for a
while.

[Victor Semaska_3]

Steven,

That was it, had to add:

--enable-languages=c++

This made it work. Thanks for all your help with this.

Vic

[Steven Schweda]

Note that once you get through the whole C
compiler build and install procedure, you
should be able to go back and re-do the whole
mess using the new GCC C compiler to build
all the other languages. (Leave out the
"CC=cc", and the "--enable-languages" bits in
the "configure" stuff.)

Now, wasn't that all about as educational as
you could stand?