Mail Archives: djgpp/1995/02/07/10:00:59
>Did you get that problem resolved somehow? If so, please
>tell me what it was and how did you solve it. If not,
>could you please post the exact command line to ld.exe
>which caused this error. (If you are invoking ld from gcc,
>then add -v to the gcc switches, and it will print the
>command line it gives to ld.)
>
>I'm the maintainer of the DJGPP FAQ list, and I would like
>to know what should one do if he gets such an error message,
>in case such a problem arises again. If you are still
>puzzled by that problem, posting more details might help
>find the solution.
As I mentioned in my first posting the only solution I found
was switching back to the old version of ld (2.4).
I just tried it again with calling ld directly:
ld -v -o test test.o -L../lib -L../../ak/lib -lak -lkern -lmms -lm -lgrx
and I get:
ld version 2.5.2 (with BFD 2.5)
../lib/libmms.a: could not read symbols: Memory exhausted
I also tried:
ld -v -o test test.o -L../lib -lmms
ld version 2.5.2 (with BFD 2.5)
../lib/libmms.a: could not read symbols: Memory exhausted
libmms.a contains 28 object-files
nm libmms.a > log
log is ~32Kb and ~1390 lines so this lib contains about 1330 symbols
If I remove 1 object of libmms
nm libmms.a >log1
log1 is ~30Kb and ~1290 lines
there's no problem (only some unresolved symbols... as expected).
Are there any restrictions about library sizes or #symbols?
go32 reports:
go32 version 1.12.maint3 Copyright (C) 1994 DJ Delorie
Lowest version I can run is 1.08
go32.exe usage: go32 [-d {debugger}] [{program} [{options} . . . ]]
go32.exe built time was Sun Dec 18 16:36:42 1994
VCPI (Expanded) memory available: 10928 Kb
Swap space available: 104796 Kb
There are 10Megs of RAM and 100Megs of Swap
I can't understand the error message: Memory exhausted
Any ideas, comments?
Thanks
Marios Siormanolakis, sior AT ira DOT uka DOT de
- Raw text -