Hi Arthur and Thiemo,
> gcc-4.2 is the default on i386, you have to switch back the default compiler
> to gcc-4.1 by hand updating /usr/bin/{cpp,gcc,g++} symlinks, etc. But you
> don't have to uninstall gcc-4.2.
Indeed; I do not have to uninstall gcc-4.2. But keeping software installed
which I an
Hi Arthur,
> It has been closed by Arthur Loiret <[EMAIL PROTECTED]> (reply to [EMAIL
> PROTECTED]).
> /usr/bin/gcc symlink is provided by `gcc' package from `gcc-default' source
> package, not by `gcc-4.2'.
Fine, you are right, the package name might be wrong, but the bug exists.
If I try to i
Package: gcc-4.1
Version: 4.1.2-19
Severity: normal
gcc-4.2 gets installed with the current 'testing' by default, but it is
not the compiler used to compile the latest 2.6 series kernel package.
Therefore gcc-4.2 is no good for compiling other modules from source
(e.g. VMware modules, uvc-video,
On Sun, Apr 25, 2004 at 11:20:53AM +0200, Matthias Klose wrote:
> gcc-3.2 did never provide a symlink to cc (handled by
> update-alternatives).
Please can you explain what exactly that means? Does it mean you have
reassigned to bug to the package containing 'update-alternatives'?
Thank you.
Sinc
Package: gcc-3.3
Version: 1:3.3.2-4
Severity: normal
After upgrading from gcc 3.2.1 to 3.3, I get the following
email from cron:
--report /etc/cron.daily
/etc/cron.daily/man-db:
mandb: warning: /usr/share/man/man1/cc.1.gz is a dangling symlink
mandb: warning: /us
5 matches
Mail list logo
