From: gboutwel <gbo...@pr...> - 2004-04-26 13:47:24
|
je...@si... wrote: > > can you disable smp and high mem. Try my .config (uml) attached. > Ummm... Did you look at the .config I attached to that e-mail? # # UML-specific options # ... # CONFIG_UML_SMP is not set # CONFIG_SMP is not set ... # CONFIG_HIGHMEM is not set Note that SMP & High Mem are disabled. I'll try your .config and let you know. George ----------------------------------------------- Get your FREE Christian Email Account at Praize http://www.praize.com/email/ |
From: gboutwel <gbo...@pr...> - 2004-04-26 18:58:19
|
Jeff, > can you disable smp and high mem. Try my .config (uml) attached. Tried your .config same thing. George ---------------------------------------------------- Need to store your files online? Upload them for free in Praize Briefcase http://www.praize.com/cgi-bin/members/mybriefcase.cgi |
From: gboutwel <gbo...@pr...> - 2004-04-30 18:31:22
|
Blaisorblade wrote: > Well, something has been *really* been messed up. If I understand > things properly, you are able to compile fine a 2.6.5 UML, right? You're telling me.. Yes I can compile an 2.6.5 host, an 2.6.5 UML, and an 2.6.6-rc1/2/3 HOST, but not an 2.6.6-rc1/2/3 guest. > The problem is that: > a) I think that file should include the "kernelspace" headers... > however the kludges needed to do it are very fragile when Kbuild changes a > bit (this problem has repeatedly showed up against Linux 2.6). Ok. If it where including kernelspace headers I don't think this would be a problem. > However, things should succeed anyway, BUT > > b) your distro headers are messed up...; the first thing I see > is that it uses the 2.6 headers. Now, the missing header should be located in > /usr/include/asm/mach-default/. Probably it is there; however the > kernel uses normally a -Iasm/mach-default, so that #include works. > Since one cannot require user programs to add -I to compile, Debian > should symlink everything from /usr/include/asm/mach-default/ into > /usr/include; As I understand it SID installs as it's 'de facto' headers not 2.6, but 2.5.999-test7. See: http://packages.debian.org/unstable/devel/linux-kernel-headers And it would seem that this area (in kernel headers) has recently changed (when compared to 2.5) or up to this point UML builds have been going against kernel provided headers instead of the 2.5 headers debian's shipping. > i.e.: > ln -s /usr/include/asm/mach-default/* /usr/include. > I'll try it, but I had really hoped not to mess with those headers as it's my understanding that important pieces of code (ie glibc, etc) are compiled against those headers. I'll write back to the list whatever I find out. Thanks, George ---------------------------- Love to laugh? Good Clean Jokes at Praize http://www.praize.com/jokes/ |
From: BlaisorBlade <bla...@ya...> - 2004-04-30 18:59:57
|
Alle 20:31, venerd=EC 30 aprile 2004, gboutwel ha scritto: > Blaisorblade wrote: > > The problem is that: > > > > a) I think that file should include the "kernelspace" headers... > > > > however the kludges needed to do it are very fragile when Kbuild > > changes a > > > bit (this problem has repeatedly showed up against Linux 2.6). > > Ok. If it where including kernelspace headers I don't think > this would be a problem. Yes, what I mean is that the proper fix is probably to make it use the kern= el=20 headers as it did before. Would you post the output of the failing make=20 command with the V=3D1 option added, to see the actual build command? > As I understand it SID installs as it's 'de facto' headers not > 2.6, but 2.5.999-test7. See: > http://packages.debian.org/unstable/devel/linux-kernel-headers > And it would seem that this area (in kernel headers) has recently > changed (when compared to 2.5) or up to this point UML builds > have been going against kernel provided headers instead of the > 2.5 headers debian's shipping. I think the 2nd thing holds, and that my suggestions is a workaround that=20 should work (I hope)... Bye =2D-=20 Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 |
From: gboutwel <gbo...@pr...> - 2004-05-04 20:06:36
Attachments:
uml-2.6.6-rc3-V.log
uml-2.6.6-rc3.log
|
> Blaisorblade wrote: > Yes, what I mean is that the proper fix is probably to make it use the kernel > headers as it did before. Would you post the output of the failing make > command with the V=1 option added, to see the actual build command? Attached is the orgianl fail (before trying the symlink in /usr/include) with V=1 as uml-2.6.6-rc3-V.log Also, attached is the new fail (after trying the symlink in /usr/include) with an V=1 as uml-2.6.6-rc3.log > I think the 2nd thing holds, and that my suggestions is a workaround that > should work (I hope)... Don't look like it. George ---------------------------------------- Single? Find Christian Singles like you! http://www.praize.com/singles/ |
From: BlaisorBlade <bla...@ya...> - 2004-05-11 18:46:48
|
Alle 22:05, marted=EC 4 maggio 2004, gboutwel ha scritto: > > Blaisorblade wrote: > > Yes, what I mean is that the proper fix is probably to make > it use the kernel > > headers as it did before. Would you post the output of the > failing make > > command with the V=3D1 option added, to see the actual build > command? > > > > Attached is the orgianl fail (before trying the symlink in /usr/include) > with V=3D1 as uml-2.6.6-rc3-V.log > > > > Also, attached is the new fail (after trying the symlink in /usr/include) > with an V=3D1 as uml-2.6.6-rc3.log > > > I think the 2nd thing holds, and that my suggestions is a workaround > > that > > > should work (I hope)... > > Don't look like it. Well, it is an improvement; try disabling the SKAS mode in the UML .config = and=20 post the new output, with V=3D1. However now I'm trying to solve the proble= m=20 myself with 2.6.6 - restart again with the patches I'm posting today (see t= he=20 "Patch for 2.6.6" thread). Bye =2D-=20 Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 |
From: gboutwel <gbo...@pr...> - 2004-05-12 15:35:09
|
bla...@ya... wrote: > Well, it is an improvement; try disabling the SKAS mode in the > UML .config and > post the new output, with V=1. However now I'm trying to solve > the problem > myself with 2.6.6 - restart again with the patches I'm posting > today (see the > "Patch for 2.6.6" thread). That failed, but see my post to the Patch for 2.6.6 thread ---------------------------- Love to laugh? Good Clean Jokes at Praize http://www.praize.com/jokes/ |