Re: [Fresco-devel] huge so's: are they normal?

"Andy Sy" <[email protected]> Thu, 6 Mar 2003 22:53:12 +0800
Newsgroups gmane.comp.video.fresco.devel
Message-ID <000b01c2e3f0$1fc9f2e0$0100a8c0@duron12>
----- Original Message ----- 
From: "Diego Sevilla Ruiz" <[email protected]>
To: <[email protected]>
Sent: Thursday, March 06, 2003 6:20 PM
Subject: Re: [Fresco-devel] huge so's: are they normal?


> Yes, I think it's typical.  What compiler are you using?  It turns out
> that in some versions (I don't know if this is the normal behavior)
> AC_PROG_CC adds "-g" automatically if it finds the gcc compiler.  Can
> you check your Fresco's config.status file to see if it contains the
> "-g" flag?:
>
> grep -e "-g" config.status
>
> If so, the big size can be caused by the debug flag. Also, you can check
> the size without debugging information by running split on those huge
> libraries.  If the size decreases, you're sure it is due to the debug
> overhead.

Ack.  Too late to find out now.  I just nuked GCC-2.95.3 and
installed GCC-3.2.2 on my Slackware box... Thanks for the advice 
anyway.  I suspect your theory is true and will try it out if 
the GCC-3.2.2 compiled Fresco so's are still unreasonably big.

By the way, do you mean strip or split?  I just learned from
a friend that you can do 'file libxxx.so' to see if an so has
been stripped or not.