Bug 86451 - ld does not recognize --stack option
Summary: ld does not recognize --stack option
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: binutils
Version: 8.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-03-22 09:18 UTC by Andrei Gaponenko
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-03-22 09:27:32 UTC
Embargoed:


Attachments (Terms of Use)

Description Andrei Gaponenko 2003-03-22 09:18:13 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513

Description of problem:
Info documentation coming with the binutils package describes
`--stack RESERVE' and `--stack RESERVE,COMMIT' options of ld.
However the linker does not recognize them. What's the way to 
request a bigger stack size? 

Version-Release number of selected component (if applicable):
binutils-2.13.90.0.2-2

How reproducible:
Always

Steps to Reproduce:
1. /usr/bin/ld --stack 10000000 ttt.o -o ttt
    

Actual Results:  /usr/bin/ld: unrecognized option '--stack'
/usr/bin/ld: use the --help option for usage information


Expected Results:  producing an executable with the requested stack size.


Additional info:

The same applies to binutils-2.11.92.0.7-1.src.rpm (RH 6.1), and 
probably to at least all versions in between.

Comment 1 Jakub Jelinek 2003-03-22 09:27:32 UTC
--stack is an PE and BeOS option only. On linux, you control the stack size
with ulimit -s (unless you use the /lib/libpthread.so.0 (not /lib/i686/libpthread.so.0)
linuxthreads implementation, which requires at most 2MB stacks).

Comment 2 Andrei Gaponenko 2003-03-22 09:34:44 UTC
Thanks for the explanation.  
Then the --stack option should be described in the "machine dependent features"
section, not in "invocation|options" of the texinfo manual.



Note You need to log in before you can comment on or make changes to this bug.