Gcc -m32 won't work according to slapt-src

[qwestion]

Ok, so I've had a pretty good time with salix. (since this is my first post, I think this would be a suitable opening note)
However, I've run into trouble with the slapt-src utility (which is awesome btw). It is telling me that gcc -m32 isn't working and that I need to install "32 bit development libraries". Hmm, well since there are thousands of those, I'm assuming it means those that gcc might use?
Basically, I'm trying to install wine and I'm not having much luck. Could you all point me in the right direction to getting it working?

[gapan]

wine is available as a binary package through slapt-get/gslapt. Why don't you use that?

[qwestion]

Ok, I don't know what wine is called in your repository (alternative to wine maybe?) but I couldn't find it in gslapt (updating didn't do anything either). That's the main reason I didn't get it from gslapt.

[gapan]

If you didn't find it, that means that you probably have a 64bit version installed. Wine is a 32bit application, it won't work in a 64bit system. Google for "slackware multilib" if you want to install 32bit libraries in your 64bit system.

[qwestion]

Thank you very much, I thought I had a serious problem.
Ok, since then, I've successfully gotten multilib working, and my installation of wine seems to have completed successfully. Only thing is, when I try to run my installer, it's telling me that I have no hard drive space...
I check, and it seems I still have 280 someodd gigabytes left (out of 320). phew. too bad, it seems that my /root = 100% full. Is this the problem? I'm really feeling like a newb here, but I'm also very anxious to get started installing this program (which has an installer in .exe form). I'm sorry if this kind of thing happens a lot and I've missed some area of the userdocs (like I did last time), but I'm really excited for what's past this hurdle!

[gapan]

What is that "my installer" you're referring to? How are you running it? Do you have a separate /root partition?

[qwestion]

My installer is an application written for 32 bit Windows that I simply need to run under wine any bugs in the installer I can handle when I get there. Even if it doesn't work under wine I still need some way of running .exe's.
I shut my computer down last night and when I tried to reboot it this morning it told me that it didn't have enough memory to mount /tmp, and now I'm reduced to the failsafe terminal.(and my Droid which isn't letting me type quickly at all) I checked on the terminal last night, and I'm pretty sure that /root is indeed mounted as a separate partition and it's 100% full. Which is odd because I don't remember setting it to be that way... is there a way to at least get my machine to work now?
Thank-you!

[gapan]

I'm guessing that you tried to install said windows application as root.
That was a bad idea, since everything you run in wine, will get
installed under ~/.wine, which means that if you're running the
installer as root, it will all end up in /root/.wine. If you have
created a small enough /root partition, that would certainly lead to
trouble. I'm guessing that's why your /root partition got filled up. All
you need to do to get it back to normal is probably:

Code: Select all

rm -rf /root/.wine

And don't ever run wine as root again.

[qwestion]

Ok, actually, it wasn't that directory that was causing this huge fiasco. It seems that my /tmp/ folder had grown too big for its britches. now I've got a script on my desktop that'll clean it every time I'm about to shut down (I will manually run the script). Thank you for your help. Oh, and I know that this probably won't sound too good, but if my installer stops, well, installing after 20 mb of data and wine tells me that it's encountered "a crucial error" or some such uninformative error (which truly gives me no idea what caused it, it's even worse than error codes) what should I do?

[gapan]

Oh, and I know that this probably won't sound too good, but if my installer stops, well, installing after 20 mb of data and wine tells me that it's encountered "a crucial error" or some such uninformative error (which truly gives me no idea what caused it, it's even worse than error codes) what should I do?

Make a bug report to the wine project.