Bug#4426: gcc bug #2

["James A. Robinson" <jimr@simons-rock.edu>]

> 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.

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... :)