./CONFIGURE error
 

I Just upgraded everything with swaret got all my DEP straight but it seems like my make and ./configure are jacked I get this error when I try to install smb4k.
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.

I just spent like 3 hours getting my Dep good what did i miss?

You have to reinstall glibc.

Just when you start thinking you got this linux thing beat and you are no longer a noob........ Well while in the midst of makeing a fresh box i removed the old linux kernel headers,source,modules. Because i compiled my kernel from kernel.org. So to everyone dont delete the kernel headers in pkgtool or youll be a dumb a.. like me.

lol, man, I've been working with Linux for nearly eight years. I learn something new every single day. I've also removed the kernel headers ;)

Dumbest thing I ever did was cleaning up my build directory after a "manual" makepkg and one of the directories was usr. So I just typed in rm -rf /usr. Right after I pressed the enter key I realized what I had just done. Should've typed in rm -rf usr, now my /usr was gone. I just popped the first Slackware CD into the CD drive and rebooted and re-installed. Luckily Slack is fairly easy to install, and I didn't format my /home drive so all my personal stuff was still there.

Live and learn,
MMYoung

I misedited the entry for root's login shell on my main production file server at my office. As soon as I saved, I closed my SSH session to try the new shell, instead of firing up a new session.

I ended up locking myself out the "brain" of the network. I had to take the server down, boot with a Live CD, chroot and edit /etc/passwd to get it up again. All while 50+ engineers waited around. ;)

I've done the exact same thing. That's kinda funny. :)

I think we ALL have done a bonehead move like that....

I remember back in '74 I just got the network for a school up. Everything was purring along, and I went to delete the 'temp' files that I had so the other dweebs wouldn't mess with it. To make a long story short, I ended up having to reprogram the main server we were using at the time (A Digital beast that you had to program with switches on the front in binary...). Sometimes, we are our worst virus....lol

It wasn't at the time, but it's a real hoot now ;).

Later,
MMYoung

I know that's right. I've often told people that the biggest program/hardware bugs I've ever seen are the ones typing on the keyboard! :D

Later,
MMYoung

My most boneheaded move was doing a "rm * -rf", then changing directories, then mistakenly grabbing the "rm * -rf" from my bash history and nuking an important directory full of unbacked up source code I had developed :S

The moral to all this is, just when you think you've done the DUMBEST, most BONEHEAD thing that you can possibly imagine... Somebody else has probably done worse and if not worse then pretty much on the same par with the DUMBA&&, BONEHEAD stunt that you just pulled.

Live and learn,
MMYoung

So true! I had to reinstall the old kernel headers again, it reminds me when i deleted e2fsprogs because it says: and i'm using reiserfs. I had to "reinstall" slackware not formating anything and installing only that package. I'm crossposting here hopefully saving somebody some time
Thanks for tip ;)