Subject: Bug#4426: gcc bug #2

From: "James A. Robinson" <[email-masked]>
Date: Fri, 06 Sep 1996 23:01:30 -0400

Package: gcc
Maintainer: David Engel <[email-masked]>
Version: 2.7.2.1-1

I don't know whether or not this is a gcc bug, but after I installed
the latest rex stuff, gcc stopped being able to find cc1.  After I
added /usr/lib/gcc-lib/i486-linux/2.7.2.1/ to my path it worked, but I
never needed to do that before (and gcc should know the path,
shouldn't it?)...

Sorry about the lack of information, but I posted a question to
debian-devel and never got a response (too much traffic I guess...).

Jim

---

From: David Engel <[email-masked]>
Date: Sun, 8 Sep 1996 17:43:55 -0500 (CDT)

> never needed to do that before (and gcc should know the path,

Are you sure you don't have another gcc or cc1 in your path?  The gcc
provided in the gcc package knows its own path.

> debian-devel and never got a response (too much traffic I guess...).

Some of us aren't on the debian-devel list and it's not by choice. :-(

David
--
David Engel                        Optical Data Systems, Inc.
[email-masked]                      1101 E. Arapaho Road
(214) 234-6400                     Richardson, TX  75081

---

From: "James A. Robinson" <[email-masked]>
Date: Sun, 08 Sep 1996 21:58:27 -0400

> provided in the gcc package knows its own path.

Ah hah! gnats or dpkg seem to be the culprite:

[lestat:~/.www/unabomber/unabomber_writings]$ locate gcc|grep "gcc$"|xargs file|grep -i exec
/usr/bin/gcc: ELF 32-bit LSB executable, Intel 80386, version 1
/usr/bin/gcc.orig-gcc: ELF 32-bit LSB executable, Intel 80386, version 1, stripped

dpkg --search gcc.orig-gcc
diversion by gnat from: /usr/bin/gcc
diversion by gnat to: /usr/bin/gcc.orig-gcc

[lestat:/home/jimr]# vi hello.c
[lestat:/home/jimr]# gcc hello.c
gcc: installation problem, cannot exec `cc1': No such file or
directory
[lestat:/home/jimr]# gcc.orig-gcc hello.c
[lestat:/home/jimr]# 

So is gnats is scr?wing over gcc?

> Some of us aren't on the debian-devel list and it's not by choice. :-(

I think newsgroups are the way to go... :)

---

From: Mark Eichin <[email-masked]>
Date: 09 Sep 1996 06:00:53 -0400

It's *gnat* , not *gnats*.  GNAT is the GNU Ada Translator; GNATS is
the Problem Report Management System :-)

If you've upgraded the gcc package to 2.7.2.1, then yes, gnat won't
work.  I suppose the next gnat package I release should have some sort
of exact-match dependency to avoid this problem, or it should drop the
override altogether (perhaps supplying an ada-gcc executable, which
would fail to compile C code if the gcc installation didn't
match... making it *much* clearer where the blame belongs.)

Go ahead and reassign this bug to gnat.  If you actually *use* gnat,
let me know, and in the meantime downgrading gcc will get it working
again.

(either very very few people use gnat, or those that do don't also
build C programs :-)

---

From: "James A. Robinson" <[email-masked]>
Date: Mon, 09 Sep 1996 07:39:36 -0400

> the Problem Report Management System :-)

Right, sorry -- I was coming down off of being wired on expresso and
not thinking/reading/associating very clearly.

> match... making it *much* clearer where the blame belongs.)

Probably...  Part of the problem is that dpkg doesn't summerize
warnings about overrides -- if I run dselect and it chugs away, I'm
likely to miss something important like this because it a) scrolls by
too quickly or b) I'm off getting a glass of water.

> let me know, and in the meantime downgrading gcc will get it working

No, I don't use it -- and I don't think anyone using my system does
either.  But thanks for the info.

Jim

---

From: [email-masked] (David Engel)
Date: Mon, 9 Sep 1996 10:44:20 -0500 (CDT)

Mark Eichin writes:
> override altogether

Please don't override the gcc from the gcc package in any case.
Instead, please send me the appropriate files to make the normal gcc
Ada-aware.  Look at how fortran is handled in the current gcc package.

> (perhaps supplying an ada-gcc executable, which

This is probably a good idea.  Gcc's handling of compiler versions is
nice for C, C++ and ObjC, since they are fully integrated, but it
breaks down horribly for other languages because of different release
cycles.

David