This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

A suggestion...


HI!
	This is not really a bug but more of a suggestion and a request for
some help. I had recently downloaded and then successfully compiled (as
per instructions in the index.html and other files) egcs-1.0.3a on a K6
@166Mhz with 32Mb RAM running Red Hat 5.0. I set the --prefix=
/usr/local/egcs/  and enabled the shared libraries. I didnt have the
right deja gnu so the test suites didnt work. I did the installation and
then egcs's g++ compiler ran very well and was much faster than the
older 2.7... gcc that i had. My problem was that after i had finished
the 'make install' part I was left with a huge directory tree in
/usr/local/egcs which took around 130MB of disk space. This along with
the 48 odd Mb taken by the source is a huge amount of space. I suggest
that the installation instructions tell one of how much HD space is reqd
to actually compile it (and possibly how much RAM is reqd). I also want
to know what directories in the 'objdir' are needed and what can be
safely deleted (or shouldnt the make file have some option to delete all
the unwanted files and just save the libraries, compilers and header
files?). For instance the objdir/gcc is a directory that takes up around
90+ MB!! Otherwise egcs seems to be great!!!

thanks in advance,

prabhu


------------- Prabhu Ramachandran ---------------------
E-mail:  prabhu@aero.iitm.ernet.in
Finger (for more info):  prabhu@www.aero.iitm.ernet.in
Home page:  http://www.aero.iitm.ernet.in/~prabhu
-------------------------------------------------------


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]