Bug#289045: gcc-3.3: gcc packages do not use the alternative system
On Fri, 7 Jan 2005 14:15:38 +0100
Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de> wrote:
> Attila Kinali wrote:
> > On Fri, 07 Jan 2005 09:56:04 +0100
> > "Falk Hueffner" <falk@debian.org> wrote:
> > > ln -s /usr/bin/gcc-3.4 /usr/local/bin/gcc
> >
> > LOL, this is a joke ? Right ?
>
> No.
I still consider it to be one.
> > Look, i don't mind if you say that the symlinks belong to the package
> > managment. I don't mind if you say i'm not supposed to touch them
> > by hand. But there is a default which version of gcc should be used.
> > And if there is a default there should be a way to change _this_
> > default _with_out_ using a workaround.
>
> Read e.g. http://bugs.debian.org/119952 for an answer.
I've read it and there is nothing that adresses any of my
argument. It just states that it doesn't fit into your
way of doing things.
Breaking things isnt an issue, because
1) There are only 2 things that can break: C++ programs
and kernel modules.
2) They can only break when compiling new programs/modules
Though I'm compiling a lot of c++ programs with different
gcc versions linking against the debian packages none of them
broke.
But when using a different compiler to compile modules than the
kernel was compiled with, things will definitly break.
3) I as an admin, want to be able to set the default compiler,
no matter what my distro was compiled with and i don't want to
mess with PATH because it doesn't fit into your way of doing things.
I want to be able to compile the kernel with that, compile my
modules, my programs, everything with _my_ default (again w/o
workarounding your "way of doing things")
Attila Kinali
Reply to: