[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#481403: marked as done (gcc-4.1 creates no gcc symlink, gcc-4.2 does)

Your message dated Thu, 15 May 2008 22:57:48 +0200
with message-id <20080515205748.GA17974@laura.lri.fr>
and subject line Re: Bug#481403: gcc-4.1 creates no gcc symlink, gcc-4.2 does
has caused the Debian Bug report #481403,
regarding gcc-4.1 creates no gcc symlink, gcc-4.2 does
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
481403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481403
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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, etc ...). Therefore gcc-4.1 needs
to be installed. And it is not unreasonable to deinstall gcc-4.2 at
the same time.

None of the above-specified kernel modules' Makefiles can find gcc
when it is called /usr/bin/gcc-4.1. It does not seem unreasonable
that Makefile writes can rely on /usr/bin/gcc or /usr/bin/cc existing.

If gcc-4.2 can create a gcc symlink then so should gcc-4.1 (obviously
subject to being the only version of gcc installed).

Clearly this is an issue that will go away as gcc-4.2 becomes the
compiler used to compile distributed kernel packages, but so long as
kernel packages are being distributed built with gcc-4.1 then this
missing symlink is a problem.

That the user has to type:

	cd /usr/bin
	ln -s gcc-4.1 gcc

should clearly not be a prerequisite to build a kernel module.

Alexis

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ISO-8859-1) (ignored: LC_ALL set to en_GB)
Shell: /bin/sh linked to /bin/bash

Versions of packages gcc-4.1 depends on:
ii  binutils            2.18.1~cvs20080103-4 The GNU assembler, linker and bina
ii  cpp-4.1             4.1.2-19             The GNU C preprocessor
ii  gcc-4.1-base        4.1.2-19             The GNU Compiler Collection (base 
ii  libc6               2.7-10               GNU C Library: Shared libraries
ii  libgcc1             1:4.3.0-3            GCC support library

Versions of packages gcc-4.1 recommends:
ii  libc6-dev                     2.7-10     GNU C Library: Development Librari
ii  libmudflap0-dev               4.1.2-19   GCC mudflap support libraries (dev

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Thu, May 15, 2008 at 09:57:34PM +0200, Alexis Huxley wrote:
> If gcc-4.2 can create a gcc symlink then so should gcc-4.1 (obviously
> subject to being the only version of gcc installed).
> 
> Clearly this is an issue that will go away as gcc-4.2 becomes the
> compiler used to compile distributed kernel packages, but so long as
> kernel packages are being distributed built with gcc-4.1 then this
> missing symlink is a problem.
> 
> That the user has to type:
> 
> 	cd /usr/bin
> 	ln -s gcc-4.1 gcc
> 
> should clearly not be a prerequisite to build a kernel module.
> 
> Alexis

/usr/bin/gcc symlink is provided by `gcc' package from `gcc-default' source
package, not by `gcc-4.2'.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: