I've found gcc here: ftp://slackware.mirrors.tds.net/pub/...1/slackware/d/

Should I just get the highest version? gcc-g77-3.3.4-i486-1.tgz
I've already encountered that I need it,sbopkg cant build NetworkManager without it, it seems.

The mouse thing, I don't know yet. I'm installing Slackware right now again on a Virtual Machine on an other (better) laptop (mostly to see if my wireless works with it) so I'll see about the mouse.

EDIT: no the above gcc is for Slackware 10.1 woops, I'll find another one

Your link points to the packages from Slackware 10.1 (long time ago).
Which version of slackware are you using (13.1?) and which architecture (32bit? 64bit)?

Haha yeah I editted my post, I've found the 13.1 version here ftp://slackware.mirrors.tds.net/pub/...1/slackware/d/

I think it has to be gcc-4.4.4-i486-1.txz right?

I have 32bit.

Something strange though, when I use cat /proc/verson it says I have gcc version 4.4.4

I thought I didnt have gcc?

I think it is just saying that your kernel was compiled with that particular version of gcc.

I'd recommend downloading and installing all gcc*.tgz files.

Dont you mean gcc.txz?

Anyway, I did that, installed the 6 gcc packages and got the following when trying to install NetworkManager with sbopkg:

configure: error: in '/tmp/SBo/NetworkManager-0.8.1':
configure: error: C Compiler cannot create executables

Edit: I read somewhere that I might be missing glibc, installed glibc-2.11.1-i486-3.txz but still the same error

Can you post more output?
edit: also try to install binutils and kernel-headers.

That sounds like twm. I would suggest only doing a partial install if you know what you're doing and know why you're not installing all the things you're not installing.

Incidentally, what makes you think sbopkg installed openbox for you?

-- edit: I missed the fact that there were two pages to this thread. Why do you say you've "found" the packages of various versions from various websites? What did you use for your install media and why don't you use that?

Hmm, I haven't installed some things yes, but that were only the Games, X apps uhm and something for mathematics. Everything that looked important, I've installed with Full install. About 5,7GB

Sorry, I meant build the package for me and I've installed it afterwards.

I've used sbopkg to get openbox only. Installed madwifi, gcc and glibc through downloading the packages myself, unpack, make, install. That's all I've installed myself.

I could use that way to download NetworkManager etc, but sbopkg is such a easier way, I just want it to work.

Well, something's gone wrong then, because you should have all the gcc* stuff from the 'd' series. The only gcc* you listed was the one from the 'x' series.

That's not what I meant. sbopkg should have installed it for you if it was built at all (you can opt not to do so, but that's not important right now). What I mean is that sbopkg couldn't have succeeded in building anything for you without the compiler and other essential elements. So I don't know what you could have installed as sbopkg would have had to have errored out when the SlackBuild itself errored out.

This would imply you did have gcc and all the required tools. So why does the ls of /var/log/packages only return gccmakedep? And what I meant by asking about "finding" things was that you said earlier in the thread that fluxbox was available on the installation CD. And then you said you "found" stuff on various ftp sites. Everything you initially need should be on the installation CD and it should have then been installed on your system. In other words, you should have no need for ftp sites - you should be able to compile things and you should also be able to run xwmconfig and choose 'fluxbox' (or edit .xinitrc to achieve the same) and do 'startx' and you should then be running fluxbox. Automatic. Then, if you really wanted openbox, the SlackBuild should Just Work and you should be able to xwmconfig/.xinitrc that the same way. Instead, it sounds like you have no other window managers installed and X is defaulting to twm. (Which would fit, since you say you didn't install 'xap' - which is a series you're likely to want much of, if not all of it.)

-- Just realized I might be misreading part of that: "Installed madwifi, gcc and glibc through downloading the packages myself, unpack, make, install." Are you saying you compiled gcc and glibc from source? That would imply you already had a working gcc. Except under extraordinary circumstances, you should always install gcc, glibc, and the like from actual Slackware binary packages. I assume that's what you did, but your phrasing could suggest otherwise.

Well, it should work. If you do have the dev tools and it did build openbox, then the aforementioned xwmconfig/.xinitrc should have it come up.

Basically, sycamorex has told you everything you need to know. It seems that there's some miscommunication somewhere if you're still having problems, which is why I'm trying to get a clearer picture of the state of your system.

Just a thought:
It seems you haven't done much configuration of the new system yet and it appears that something has indeed been 'lost in translation'. It might be difficult to get to the bottom of the problem. Perhaps, the quickest and easiest solution would be to do a fresh FULL slackware install. That would save you a lot of hassle.

Thank you both for the reply. If I remember correctly I've installed these packages: A, K, L, N, X.

And somehow I REALLY did get openbox with sbopkg with only gccmake-dep-1.0.2-noarch-2 after I did: ls /var/log/packages | grep gcc

So, to start all over, please tell me which of these I deffinitely need: http://www.slackware.com/install/softwaresets.php

sbopkg is miraculously good.

That's an out of date list in that gnome no longer exists. For the current sets

a - required for anything and everything
ap - required to do much on the command line
d - required for development (including compiling from source)
e - not at all required
f - not required unless you lack a net connection and want a lot of mostly out-of-date docs
k - required for some compiling
kde - not at all required
kdei - only needed if you use kde and need i18n
l - required to do much compiling and can include some libs not in aaa_elflibs
n - required to do much networking
t - required to build some documentation even if you don't need it otherwise
tcl - needed in odd little places but not generally needed
x - required to have X
xap - required to do much with X
y - not required

Long story short, you should install everything but emacs (e), faqs (f), and kde|kdei but, if you really insist on shaving off sets, then you can dump bsd-games (y), probably tcl, and possibly tetex (t). If you really want to save more space, you can shave individual packages within sets. But unless you are really completely out of disk space and really know what everything does, I would recommend (as I already have) a full install.

To underline the stuff you need for your present purposes: you really need d and l and say you don't have d.

And I agree with sycamorex though I hate to suggest it - you might be better off starting over with a fresh full install - I mean, there would be nothing wrong with simply adding the sets you need to this install - there's likely no need for a clean install. It would just be for clarity's sake to make sure you knew what you had and had what you needed. I'd recommend keeping an 'install log' of your own and then keeping up with it as a system ChangeLog so that you know what you've done. "If I remember correctly I've installed these packages: A, K, L, N, X." That never works for me because I rarely remember correctly.

Thanks for the reply. I've followed the advice of doing a clean install. Installed everything except E, F, KDE, KDE and Y, like you said. This time I got a screen of which windows manager I wanted, that didn't come up in my first install. I picked Fluxbox. I only want Openbox because I have (some) experience with it and I liked it, but Fluxbox seems to be fine too, for now.

Now it should be just a question of getting sbopkg and then installing openbox. Afterwards you'd run xwmconfig.