Re: [Cooker] why the different versions??
--- Juan Quintela [EMAIL PROTECTED] wrote: running a glibc and different kernel-headers for the ones that you used to compile glibc can harm. Do you happen to know how? I know that's the reason always given, but I've done it for years with no problems. Also, you could still do it the way you're doing it without putting kernel-headers in glibc's SRPM. __ Do You Yahoo!? Yahoo! Movies - coverage of the 74th Academy Awards® http://movies.yahoo.com/
Re: [Cooker] why the different versions??
At 06:52 PM 3/25/02, you wrote: --- Juan Quintela [EMAIL PROTECTED] wrote: running a glibc and different kernel-headers for the ones that you used to compile glibc can harm. Do you happen to know how? I know that's the reason always given, but I've done it for years with no problems. Also, you could still do it the way you're doing it without putting kernel-headers in glibc's SRPM. I have understood that the reason has to do with alignment of structure elements. If a program fills in a structure with the definition from one header file and then calls a function that used a different (and _incompatible_) version of the structure, then all sorts of problems can occur. My guess is that most structures are quite stable so the likelihood of getting into trouble is pretty low.
Re: [Cooker] why the different versions??
On 2002.03.25 Kevin Krumwiede wrote: Because kernel-headers are needed far oftener than glibc-devel. And it they are always required, why do not include them just with glibc-devel ??? Nope: - You SHOULD NOT be compiling kernel modules against kernel-headers in /usr/include, but against kernel-source in /usr/src/linux (that of course includes one other copy of the headers, and that can be different from those in /usr/include). - For user-space compiles (which is the most common case), you need glibc headers that use kernel-headers in /usr/src. So: - You always need kernel-headers to build user-spaces apps. - They are different from those in /usr/src/linux. - They do not change if you upgrade kernel. You can't live without them. Just include them in glibc-devel. Less headaches. -- J.A. Magallon # Let the source be with you... mailto:[EMAIL PROTECTED] Mandrake Linux release 8.3 (Cooker) for i586 Linux werewolf 2.4.19-pre4-jam2 #1 SMP Mon Mar 25 01:34:14 CET 2002 i686
Re: [Cooker] why the different versions??
On 2002.03.26 J.A. Magallon wrote: - For user-space compiles (which is the most common case), you need glibc headers that use kernel-headers in /usr/src. ^ This is obviously ... /usr/include/... -- J.A. Magallon # Let the source be with you... mailto:[EMAIL PROTECTED] Mandrake Linux release 8.3 (Cooker) for i586 Linux werewolf 2.4.19-pre4-jam2 #1 SMP Mon Mar 25 01:34:14 CET 2002 i686
Re: [Cooker] why the different versions??
david == David Walser [EMAIL PROTECTED] writes: david --- Juan Quintela [EMAIL PROTECTED] wrote: running a glibc and different kernel-headers for the ones that you used to compile glibc can harm. david Do you happen to know how? I know that's the reason david always given, but I've done it for years with no david problems. Also, you could still do it the way you're david doing it without putting kernel-headers in glibc's SRPM. Hi glibc is supposed to work with several kernels. In particular it hands things like running on top of kernel 2.2 kernel 2.4. Some structs other ABIs have changed bettewn then (and in the middle of the 2.4 series). If you glibc is compiling thinking that sizeof(struct foo) = 64 and then you change kernel-headers and sizeof(struct foo) = 70, you have just broken any application that uses a library compiled against glibc with old hearders and the new compiled code. Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy
Re: [Cooker] why the different versions??
michael == Michael Dransfield [EMAIL PROTECTED] writes: michael I have noticed that the package for kernel headers is different to all michael the other kernel versions (2.4.18-25mdk, not 2.4.18.6mdk-1-1mdk) michael kernel-2.4.18.6mdk-1-1mdk.i586.rpm michael kernel-enterprise-2.4.18.6mdk-1-1mdk.i586.rpm michael kernel-headers-2.4.18-25mdk.i586.rpm michael kernel-secure-2.4.18.6mdk-1-1mdk.i586.rpm michael kernel-smp-2.4.18.6mdk-1-1mdk.i586.rpm michael This causes problems with recompiling a vmware kernel. It complains michael that they are different versions and will not be able to compile a new michael kernel module. michael There must be a valid reason for this... but I cant find why. Are they michael the headers used to build this kernel? There are two things with headers: - they came from kernel - they are used by glibc running a kernel and a different kernel-headers is right running a glibc and different kernel-headers for the ones that you used to compile glibc can harm. That made that know glibc provides the headers that it has compiled against. This let less space for errors. Later, Juan. -- In theory, practice and theory are the same, but in practice they are different -- Larry McVoy
Re: [Cooker] why the different versions??
On Mon, Mar 25, 2002 at 03:44:29PM +0100, Juan Quintela wrote: There are two things with headers: - they came from kernel - they are used by glibc running a kernel and a different kernel-headers is right running a glibc and different kernel-headers for the ones that you used to compile glibc can harm. That made that know glibc provides the headers that it has compiled against. This let less space for errors. This makes sense but why not name kernel-headers: glibc-kernel-headers I think it would decrease the confusion here. -- Ben Reser [EMAIL PROTECTED] http://ben.reser.org What difference does it make to the dead, the orphans, and the homeless, whether the mad destruction is wrought under the name of totalitarianism or the holy name of liberty and democracy? - Ghandi
Re: [Cooker] why the different versions??
On 2002.03.25 Ben Reser wrote: On Mon, Mar 25, 2002 at 03:44:29PM +0100, Juan Quintela wrote: There are two things with headers: - they came from kernel - they are used by glibc running a kernel and a different kernel-headers is right running a glibc and different kernel-headers for the ones that you used to compile glibc can harm. That made that know glibc provides the headers that it has compiled against. This let less space for errors. This makes sense but why not name kernel-headers: glibc-kernel-headers I think it would decrease the confusion here. And it they are always required, why do not include them just with glibc-devel ??? -- J.A. Magallon # Let the source be with you... mailto:[EMAIL PROTECTED] Mandrake Linux release 8.3 (Cooker) for i586 Linux werewolf 2.4.19-pre4-jam2 #1 SMP Mon Mar 25 01:34:14 CET 2002 i686
RE: [Cooker] why the different versions??
Because kernel-headers are needed far oftener than glibc-devel. And it they are always required, why do not include them just with glibc-devel ???
Re: [Cooker] why the different versions??
On 23 Mar 2002 09:52:50 + Michael Dransfield [EMAIL PROTECTED] wrote: I have noticed that the package for kernel headers is different to all the other kernel versions (2.4.18-25mdk, not 2.4.18.6mdk-1-1mdk) kernel-2.4.18.6mdk-1-1mdk.i586.rpm kernel-enterprise-2.4.18.6mdk-1-1mdk.i586.rpm kernel-headers-2.4.18-25mdk.i586.rpm kernel-secure-2.4.18.6mdk-1-1mdk.i586.rpm kernel-smp-2.4.18.6mdk-1-1mdk.i586.rpm kernel-headers are actually part of glibc, so therefore the different release number. There should be enough about it in the archives of cooker. This causes problems with recompiling a vmware kernel. It complains that they are different versions and will not be able to compile a new kernel module. You need kernel-source for kernelmodules like vmware, and compile it on the headers of /usr/src/linux-version/include. -- Marcel Pol Linux 2.4.18-5mdksmp, up 13 days, 14:22
