From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Kettle To: gcc Subject: linking egcs code on the DEC Date: Thu, 09 Sep 1999 10:43:00 -0000 Message-id: <060FA37D7F0F200B*/c=US/admd=400net/prmd=abnamro/o=notes/s=Kettle/g=Steve/@MHS> X-SW-Source: 1999-09/msg00362.html Hi, I've been writing source code on the DEC using egcs for a few months now. I'm using 2.91.60 version. The problem is that the -g option makes the object files so large that the linker is running out of memory during the link phase. The linker being used is the native linker - and I think that gnu doesn't have a version of the gnu-linker for the dec - if it did I could using the gnu linker option that does not load all the object files into memory. Does anyone know of a work around to this problem. Here are some of the solutions I've been trying: - use the -gcoff instead of -g : but this causes gdb to go haywire when debugging C++. - buy more memory or increase swap ( may be no budget for this ) - upgrade to new version of egcs - (is this bug fixed ??? ) - is there a option to DEC ld which does not cause everything to be loaded into memory ? The problem is the app is just a medium sized application but the link process grows above 200 megs. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Kettle To: gcc Subject: linking egcs code on the DEC Date: Thu, 30 Sep 1999 18:02:00 -0000 Message-ID: <060FA37D7F0F200B*/c=US/admd=400net/prmd=abnamro/o=notes/s=Kettle/g=Steve/@MHS> X-SW-Source: 1999-09n/msg00362.html Message-ID: <19990930180200.qD5Pv4LUc3zE_iYm_P7RV_blkQUUEUweSMJa1W_m1To@z> Hi, I've been writing source code on the DEC using egcs for a few months now. I'm using 2.91.60 version. The problem is that the -g option makes the object files so large that the linker is running out of memory during the link phase. The linker being used is the native linker - and I think that gnu doesn't have a version of the gnu-linker for the dec - if it did I could using the gnu linker option that does not load all the object files into memory. Does anyone know of a work around to this problem. Here are some of the solutions I've been trying: - use the -gcoff instead of -g : but this causes gdb to go haywire when debugging C++. - buy more memory or increase swap ( may be no budget for this ) - upgrade to new version of egcs - (is this bug fixed ??? ) - is there a option to DEC ld which does not cause everything to be loaded into memory ? The problem is the app is just a medium sized application but the link process grows above 200 megs.