Bug#488343: linux-headers-2.6.24-1-686: useless dependency on gcc-4.1
Daniel because you need to use the same compiler version that was used Daniel to build the kernel in order to build modules against the Daniel headers. I didn't know that. Since when is this the case? Is this enforced by the upstream kernel, or is it an artifact of the Debian infrastructure? If I do build modules from source (in my case, alsa, which was recommended to me by the Debian alsa maintainers) this seems to give me the choice between: 1/ build the entire kernel from source as well, or 2/ keep an open-ended set of GCC versions around just in case a packaged kernel comes around that was compiled with it and I have to recompile the modules with the same version. Am I missing something? i -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488343: linux-headers-2.6.24-1-686: useless dependency on gcc-4.1
Package: linux-headers-2.6.24-1-686 Version: 2.6.24-7 Severity: minor Why? Eevn if you must depend on a compiler (and I don't see that, either), why won't just any version of gcc do? -- 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=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-headers-2.6.24-1-686 depends on: ii gcc-4.1 4.1.2-22 The GNU C compiler ii linux-headers-2.6.24-1-common 2.6.24-7 Common header files for Linux 2.6. ii linux-kbuild-2.6.24 2.6.24-1 Kbuild infrastructure for Linux 2. linux-headers-2.6.24-1-686 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488343: linux-headers-2.6.24-1-686: useless dependency on gcc-4.1
* Ian Zimmerman [EMAIL PROTECTED] [2008-06-27 23:04]: Why? Eevn if you must depend on a compiler (and I don't see that, either), why won't just any version of gcc do? Because you have to use the same compiler version that was used to compile the kernel in order to compile modules. And the linux-headers package allows you to compile modules, so it makes sense to depend on the gcc version used to compile the kernel. You don't have to install linux-headers though. The linux-image package doesn't depend on it. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488343: linux-headers-2.6.24-1-686: useless dependency on gcc-4.1
Ian Zimmerman wrote: Why? Eevn if you must depend on a compiler (and I don't see that, either), why won't just any version of gcc do? because you need to use the same compiler version that was used to build the kernel in order to build modules against the headers. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#488343: linux-headers-2.6.24-1-686: useless dependency on gcc-4.1
On Sat, Jun 28, 2008 at 08:49:46AM +0200, Martin Michlmayr wrote: Because you have to use the same compiler version that was used to compile the kernel in order to compile modules. This is only true on ia64 currently. The other arches stopped embedding the compiler version in the module ABI. And the linux-headers package allows you to compile modules, so it makes sense to depend on the gcc version used to compile the kernel. The kernel still have stricter requirements for the compiler, so the forced usage of the same compiler is the IMHO best/easiest way to stop people doing stupid things. Bastian -- Another dream that failed. There's nothing sadder. -- Kirk, This side of Paradise, stardate 3417.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
