Trouble untar-ing gcc, unknown filetype

[Steven Schweda]

Depending on your endurance, there may be a
couple more possibilities.

As I already had an older GCC C compiler
available, my recent GCC 3.4.6 build used
that one, so that probably helped in my case.
As "ptrmismatch" and "ptrmismatch1" seem (in
my experience) to be among the most common
complaints spewed by DEC/Compaq/HP C (on both
VMS and Tru64) when they are used on the
typical piece of (GNU-compatible) free
software, I can't say that I'm amazed by this
one.

I haven't tried it (lately?), but it should
be possible to go back to the beginning,
define an environment variable "CC" to be a
"cc -whatever" command which will disable
those warnings, and then re-run the
"configure" script, and take another whack at
it. (I'd fill in the details, but my Tru64
system is down now, and I don't have a Tru64
C guide handy. On VMS, it's "/WARNINGS =
(DISABLE=(ptrmismatch, ptrmismatch1))".
It's probably vaguely similar on Tru64.)

The code which triggers these complaints is
almost always harmless, so it's a pretty safe
work-around.

Alternatively, if you're really desperate, I
could probably box up my gcc-3.4.6_obj
directory, and leave it on my FTP/HTTP server
for a while. Send e-mail to
"sms@antinode-org" (more or less) to start
that option. It won't be small, of course,
but bzip2 compression is ok, right?

Of course, it's your life, and you're welcome
to reclaim whatever's left of it at any time.

[Steven Schweda]

For fun -- I'm easily entertained -- I tried
building GCC 3.4.6 starting with "cc" instead
of "gcc", and it seemed to work fine. The
sequence was:

mkdir gcc-3.4.6_obj2
cd gcc-3.4.6_obj2
CC=cc ../gcc-3.4.6/configure
gmake bootstrap-lean

It seemed to be using "cc" in the early
stage, as expected, so I'm rather at a loss
to explain a failure in this situation.
Perhaps your prayers have been directed at
the wrong deity.

Around here:

urtx# sizer -v
Compaq Tru64 UNIX V5.1B (Rev. 2650); Sat Jan 28 11:47:04 CST 2006

urtx# cc -V
Compaq C V6.5-303 (dtk) on Compaq Tru64 UNIX V5.1B (Rev. 2650)
Compiler Driver V6.5-302 (dtk) cc Driver

urtx# $SHELL --version
GNU bash, version 3.1.1(1)-release (alpha-dec-osf5.1)
Copyright (C) 2005 Free Software Foundation, Inc.

[Steven Schweda]

And the magic C compiler option appears to be:

-msg_disable=ptrmismatch,ptrmismatch1

but I haven't actually tried it.

[Victor Semaska_3]

Steven,

Thanks for hanging in there. First I installed bash so as to have a similar environment, I was using ksh. I followed your steps and got the same error. I tried to use the -msg_disable option but it didn't work. Maybe it's the syntax.

bash-3.00# CC=cc ../gcc-3.4.6/configure -msg_disable=ptrmismatch,ptrmismatch1
configure: error: -msg_disable=ptrmismatch,ptrmismatch1: invalid option; use --help to show usage

bash-3.00# sizer -v
Compaq Tru64 UNIX V5.1B (Rev. 2650); Wed Mar 8 14:45:28 EST 2006

bash-3.00# cc -V
Compaq C V6.5-011 on Compaq Tru64 UNIX V5.1B (Rev. 2650)
Compiler Driver V6.5-003 (sys) cc Driver

bash-3.00# bash --version
GNU bash, version 3.00.0(1)-release (alphaev67-dec-osf5.1)
Copyright (C) 2004 Free Software Foundation, Inc.

Vic

[Victor Semaska_3]

Figured out the options problem, had to:
$ CFLAGS="-msg_disable ptrmismatch,ptrmismatch1"
$ export CFLAGS

Then do:
$ CC=cc ../gcc-3.4.6/configure

But it still fails:
cc -msg_disable ptrmismatch,ptrmismatch1 -DIN_GCC -DHAVE_CONFIG_H -o cc1plus \
cp/call.o cp/decl.o cp/expr.o cp/pt.o cp/typeck2.o cp/class.o cp/decl2.o cp/error.o cp/lex.o cp/parser.o cp/ptree.o cp
/rtti.o cp/typeck.o cp/cvt.o cp/except.o cp/friend.o cp/init.o cp/method.o cp/search.o cp/semantics.o cp/tree.o cp/repo.o cp/dump.o
cp/optimize.o cp/mangle.o cp/cp-lang.o cp/name-lookup.o cp/cxx-pretty-print.o attribs.o c-common.o c-format.o c-pragma.o c-semantics
.o c-lex.o c-dump.o c-pretty-print.o c-opts.o c-pch.o c-incpath.o cppdefault.o c-ppoutput.o c-cppbuiltin.o prefix.o main.o libbacke
nd.a libcpp.a ../libiberty/libiberty.a ../intl/libintl.a -liconv
cc -c -msg_disable ptrmismatch,ptrmismatch1 -DIN_GCC -DHAVE_CONFIG_H -I. -If -I../../gcc-3.4.6/gcc -I../../gcc-3.4.6/gcc/f
-I../../gcc-3.4.6/gcc/../include -I../intl ../../gcc-3.4.6/gcc/f/bad.c -o f/bad.o
cc: Error: ../../gcc-3.4.6/gcc/f/proj.h, line 37: #error "You have to use gcc 2.x to build g77." (errormessage)
#error "You have to use gcc 2.x to build g77."
--^
gmake[1]: *** [f/bad.o] Error 1
gmake[1]: Leaving directory `/cluster/members/member0/tmp/gcc-3.4.6_obj2/gcc'
gmake: *** [all-gcc] Error 2

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

Vic

[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?