On Sun, Jun 01, 2003 at 08:56:47PM +0200, Gavrila wrote:
> Il dom, 2003-06-01 alle 20:04, roverr ha scritto:
> > I see someone has already filed bug 195682 against gcc-3.3.
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=195682
>
> Dunno if it's a gcc problem. I mean if gcc put on another par
> I haven't needed to try this yet, but I suspect you could insert a line
> "CC=gcc-3.2" in /etc/kernel-pkg.conf to compile your kernels with gcc-3.2
> even if your system's default compiler were gcc-3.3.
seems like a good idea, I'll try it the next time I recompile a kernel
> I don't see why you
On Sun, 01 Jun 2003 21:54:07 +0200
Joris <[EMAIL PROTECTED]> wrote:
> shouldn't there be a 'Debian way' of doing this? if the old gcc-packages
> were still on the server (or if you don't apt-get clean so often :-)), one
> could do
> $ sudo apt-get install gcc=3.2
> $ echo gcc hold | sudo dpkg --se
On Sun, 1 Jun 2003 21:56:59 +0100
Colin Watson <[EMAIL PROTECTED]> wrote:
> (The long-term solution is to fix the kernel.)
Is the current gcc-3.3 situation like the infamous binutils "bug" a while
back?
Kevin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trou
On Sun, Jun 01, 2003 at 09:54:07PM +0200, Joris wrote:
> shouldn't there be a 'Debian way' of doing this? if the old gcc-packages
> were still on the server (or if you don't apt-get clean so often :-)), one
> could do
> $ sudo apt-get install gcc=3.2
> $ echo gcc hold | sudo dpkg --set-selections
>
> Yep, if u want to resolv this problem, link gcc against gcc-3.2 instead
> of gcc-3.3.
shouldn't there be a 'Debian way' of doing this? if the old gcc-packages
were still on the server (or if you don't apt-get clean so often :-)), one
could do
$ sudo apt-get install gcc=3.2
$ echo gcc hold | sud
Il dom, 2003-06-01 alle 20:04, roverr ha scritto:
> I've noticed the same thing after I upgraded to gcc-3.3 on Sarge
> today.
> I can compile kernel an x86 2.4.20 kernel if I point /usr/bin/gcc to
> gcc-2.95.
> With /usr/bin/gcc -> gcc-3.3 my kernel compile fails with the
> following:
>
> gcc -D__
I've noticed the same thing after I upgraded to gcc-3.3 on Sarge today.
I can compile kernel an x86 2.4.20 kernel if I point /usr/bin/gcc to
gcc-2.95.
With /usr/bin/gcc -> gcc-3.3 my kernel compile fails with the following:
gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.20/include -Wall
-Wstrict-pr
Hi,
Jan Willem Stumpel wrote:
> -- is this normal (so many different gcc's)?
yes.
> -- isn't this a PITA?
no.
> -- what documentation should an ordinary user have read, in order
>to know about this?
> -- what should I leave the symlink at?
3.3
And edit HOSTCC in Linux' Makefile.
(or if y
9 matches
Mail list logo
