home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.sysv386:12530 comp.unix.questions:9480 comp.unix.programmer:3955
- Path: sparky!uunet!mcsun!Germany.EU.net!unido!kommu!orion!wp
- From: wp@orion.erls01.siemens.de (Wolfgang Prediger)
- Newsgroups: comp.unix.sysv386,comp.unix.questions,comp.unix.programmer
- Subject: Re: What causes this ld error?
- Message-ID: <514@kommu.UUCP>
- Date: 28 Jul 92 11:45:26 GMT
- References: <1992Jul27.205816.20382@bradley.bradley.edu>
- Sender: news@kommu.UUCP
- Reply-To: wp@orion.erls01.siemens.de
- Followup-To: comp.unix.sysv386
- Organization: SIEMENS AG, AUT 482, Nbg-M
- Lines: 40
- X-Newsreader: Tin 1.1 PL4
-
- guru@camelot.bradley.edu (Jerry Whelan) writes:
- : I'm building a debugged version of MoNet (a network monitor
- : program) on the following system:
- :
- : AT&T 386-33 w/ 16 meg of RAM and 32 meg of swap.
- : AT&T SVR4 2.0.1
- : X11r5 pl13
- : gcc 2.2.1
- :
- :
- : When I do the final link stage for certain programs
- : (xmonet for example) I get this error:
- :
- : ld: xmonet: libelf error: Memory error: output file space elf_update:
- :
- [ ... ]
- Some months ago, I've got the same error installing (linking) some
- executables of Oracle rdbms on SVR4 (SNI MX500-90).
- I could fix it by increasing the DAT- and VMMLIM to the maximum value
- (see /etc/conf/cf.d/{m,s}tune).
-
- This part in my stune:
-
- SVMMLIM 0x7FFFFFFF
- HVMMLIM 0x7FFFFFFF
- SDATLIM 0x7FFFFFFF
- HDATLIM 0x7FFFFFFF
-
- Maybe, these values are too big, but who can afford the time
- to build a lot of kernels to find out real 'good' ones ?!
-
- Hope this helped you
-
- - Wolfgang
- --
- Name : Wolfgang Prediger
- Email: wp@orion.erls01.siemens.de
- Snail: Siemens AG, AUT 482, Gleiwitzer Str. 555, 8500 Nuernberg Germany
- Voice: +49 911 895 3155 (work)
- --- "Beam me up, Scotty, there's no intelligent life down here !" ---
-