On Sunday 30 November 2003 17:34, Dennis Robertson wrote: > From: "Jason Stubbs" <[EMAIL PROTECTED]> > Sent: Sunday, November 30, 2003 11:54 AM > > On Sunday 30 November 2003 10:43, Dennis Robertson wrote: > > > On google someone suggests the latest headers are broken and to use > > > version 2.4.19-r1.ebuild. I have this version installed. > > > > Are you sure it's not slotted? i.e. are there any other linux-headers > > installed? If there are, then the other ones have probably overwritten > > your 2.4.19 headers. To rectify, remove them all and reinstall 2.4.19. > > Sorry, Jason, can you please expand on how to check and replace. I simply > did an emerge -Cvp linux-headers and the response was to R 2.4.19. I assume > that means it is installed.
If it only lists 2.4.19 then that's the only one installed. > > > Someone else suggests changing the kde-libs ebuild to include > > > --disable-strict and --disable-warning. I tried this with a crash at the > > > same point. > > > > If this didn't work, then it sounds like the error your getting is > > different to the error that the above two suggestions are meant to fix. > > Can you post the output just to confirm? > > The output is as stated in my post. You mean the following? Error kde-base/kde-libs-3.1.4 failed Function kde_src_compile, line 137,Exitcode2 died running emake, kde_src_compile: make. That's just the output from emerge; it doesn't say anaything about what the error was other than Exitcode2. Above that, you should see normal compilation output followed by a line that says Error at line xx in file xxxx after which should be the actual error. After that there will be a whole bunch of warnings and finally it will say that make exited with error code 2. Then it will list exiting a whole heap of directories and eventually the output you gave above. The information needed to help fix the problem is the Error at line xx in file xxxx and the description of the error in the following line(s). Jason -- [EMAIL PROTECTED] mailing list
