Hello all. I was trying to compile a kernal in Slackware 14 this evening, following the write up found http://blog.tpa.me.uk/slackware-kernel-compile-guide/ there. I get to the "make -j7" part, it begins to work then...
What am i missing?

Can you post the exact command you typed please? It looks like the default hostname (darkstar) was pasted in somewhere. Have you changed any environment variables or config file values (apart from the make menuconfig part)?

I used the default DarkStar name here in place of <LocalVersion> in that line. "where <LocalVersion> is the string you added in the kernel config LocalVersion option." Excerpt from the site I referenced. Did I use the wrong syntax in something?

That looks fine - if you've re-run the commands and gotten the same error I'd have a look in /usr/src/linux-3.2.29/scripts/gcc-version.sh and see what lines 25 & 26 are doing. The inputs it uses might give a clue as to what has happened.

Well, I didn't download any new source for the kernal or anything, just using what i had. I'll compile a new 3.11 kernal and go from there. Will post results. Thanks for reading!

Now, downloaded the new source. Compiled, and failed to get it to boot. Lol. Figured that out, recompiled, now it won't load my wireless card module, and in Menuconfig, I can't seem to find what I'm looking for. Wireless loads just fine when I boot from the emergency usb stick i made, thank god. But my new kernel doesn't seem to find my wireless card now. The results from
lspci -nn -s 03:00.0
returns
03:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4227] (rev 02)

Is it possible to insert this as a module, without having to compile the kernel (again)?

Also, when loading the default kernel (3.2.29) I see that the Fuse module loads without a problem. On my new kernel (3.11.1), I see Fuse module fails to load. I didn't see an option in Menuconfig when I compiled to enable this or the wireless module. What am I doing wrong? This is an older IBM Lenovo R61 that I'm using, so a smaller, faster kernel with as many modules compiled in would be best (not changing hardware and such). Any help at all would be great. If anything, just tell me how to get the information you need to help (logs, error messages and such).

Used this site this time for my kernel info

Bump

Ok, so kernel compiled, wifi issue solved, bluetooth is not currently working. Not a big issue, won't be much use to me. Now, my cd/rw drive won't burn any cd's unless i'm root. Not so much that it won't burn, as k3d doesn't even recognize that i have a cd burner. Now, i use Xfce window manager. When i put a cd in the drive on the root account, it automatically shows up on the desktop and in the file manager. That's all good. When mounted as a regular user, tho, it pops up 2 icons on the desktop and filemanager, and is mounted in /run/media it think, not /mnt/cdrom. This is the point when, when starting K3B, is says there is no optical drives installed. It seems to me that it sees my cdrom as a usb drive, not optical, when using the normal user account.
Thanks for your help in advance. Maybe i'll get it figured out before i come back

Oh, btw, is there any way to probe ALL my hardware so I can get a list and compile this kernel one more time without missing anything?

Bump

Greetings
I can't help you with any answers yet. All I can do is add to the list of complainers about K3B. Mine worked fine originally and seemed to no longer recognize my Plextor SATA DVD burner after upgrading to kernel version 3.12. I don't know with any level of certainty that these are related as I don't burn that often and don't upgrade kernel more than around 3 times per year.

FWIW I used "make oldconfig" first employing zcat or running config and only accepted a few new items, mostly as modules. So far I can't see how adding on would break K3B but I do want to find out, and one way or another, I will. Google so far returns many "not recognize" issues with K3B across many distros and kernels. Hmmmmm

You might check the dvd device and be sure it can be written to. Sometimes udev (or whatever you are using to create /dev) will get the access mask incorrect, and k3b can't write to it.