LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 03-01-2004, 11:07 PM   #1
insectile
LQ Newbie
 
Registered: Feb 2004
Posts: 20

Rep: Reputation: 0
Recompile glibc with larger stack size?


Hi all -

I've seen the root of my problem mentioned before, but no one has posted a clear solution.

Primer: WineX is a program used to run windows games under linux. It is like Wine, but works better for games (generally). I enjoy using it despite the fact that many people have reasons for feeling it is evil.

Basically I like to use WineX, and I have just moved to using Slackware (9.1 with kernel 2.6.3). WineX warns me that because of the version of glibc I am using, it has to use pthreads, and then it claims that my stack size is too small for some games (there is an actual test you can run to verify this which fails even if I run it after running ulimit -a).

Transgaming (the people who make WineX) say that the only solution at this time is to recompile glibc with a larger default stack size. They also warn that this is not an easy task.

While it would be nice if someone had a step by step guide for me to use, I don't expect that. What I am posting for is to get some advice:

1. Is recompiling glibc with a larger default stack size really that hard?
2. Will it affect anything else that I should be aware of (ie. will stability be compromised or will other components require a recompile)?
3. Is there any advice I can get of any kind? I'll read and do my part, I just want to know if there are any gotchas out there for this or if anyone has anything to tell me that might save me a few hours of reading/experimenting.


Thanks all.

bug

ps - Slack is just crazy good - just came from Fedora and this is a whole new experience. Dropline gnome is so sexy and slack is NOT hard to deal with at all. I always felt Fedora was fighting me and slack just rolls with me. Too bad people are scared off by the rep.
 
Old 07-01-2004, 12:25 AM   #2
subaruwrx
Member
 
Registered: Mar 2004
Distribution: Ubuntu Feisty
Posts: 641

Rep: Reputation: 30
Encountered this problem too.

Anyone got solution?
 
Old 07-01-2004, 07:29 AM   #3
Toth
Member
 
Registered: Aug 2003
Posts: 83

Rep: Reputation: 15
Quote:
1. Is recompiling glibc with a larger default stack size really that hard?
Nope. Just grab the glibc directory /source/l from your favorite mirror. Included in the directory is a SlackBuild script. Edit it to add the necessary option to the ./configure line to increase the stack size. Also, set the BUILD environment variable to "6custom" or "6(initials)" or something similar, assuming 6 is the current build revision (to find out, 'ls /var/log/packages | grep glibc' it'll be the last number in the glibc package output. Also, you can set the ARCH environment variable to get a small amount of optimization, or edit the script to add your own optimizations (though this can be dangerous). Though, I've read that optimizing the kernel and glibc will give good speed boosts, and most other packages aren't worth optimizing. Then execute the script. This will compile glibc and create a series of packages which you can then use with upgradepkg to upgrade to your custom glibc.

Code:
# ARCH="i686" BUILD="6a" ./SlackBuild
Then upgrade to the packages it generates, and you should be set.

EDIT: I'm assuming above that changing the default stack size in glibc is simply a matter of passing it a configure option. That may or may not be the case, though I assume there is such a configure option.

Quote:
2. Will it affect anything else that I should be aware of (ie. will stability be compromised or will other components require a recompile)?
That I don't know.

Quote:
3. Is there any advice I can get of any kind? I'll read and do my part, I just want to know if there are any gotchas out there for this or if anyone has anything to tell me that might save me a few hours of reading/experimenting.
Hopefully the SlackBuild script will ease things for you a bit, but other than that I've never bothered trying to rebuild glibc in Slackware.

Last edited by Toth; 07-01-2004 at 07:31 AM.
 
Old 07-20-2004, 01:34 PM   #4
vrln
Member
 
Registered: Mar 2004
Location: Finland
Distribution: Gentoo
Posts: 235

Rep: Reputation: 30
I have this problem too, cedega 4.0 complains about this, although warcraft 3 at least seems to work perfectly. I tried to read http://www.gnu.org/software/libc/libc.html but couldn't find anything related to changing stack size. And there are some warnings that compiling the library is not easy etc... Anyone tried it yet?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Default stack size on Linux/glibc/pthreads? rameshnj Linux - Newbie 3 11-03-2009 03:55 AM
FC4 - new stack size? DJOtaku Fedora 2 10-07-2005 01:22 PM
2052 stack size is not enough! - glibc problem Yerp Linux From Scratch 2 12-26-2004 04:12 PM
Stack Size Decision atul_mehrotra Linux - General 0 10-07-2004 02:01 AM
file system size larger than fysical size:superblock or partition table corrupt klizon Linux - General 0 06-18-2004 05:18 PM


All times are GMT -5. The time now is 11:03 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration