No Subject

The size I gave was the executable file size.  Half the problem is 
understanding out what I should be looking at; the other half is 
figuring out the binutils and/or HP-UX command that will show it.

>From 'size -v', there's no one section that's responsible.  Most of them 
have grown some.  But the total section sizes don't correspond to the 
file sizes: 'size' reports 4818 & 5957 for the two gcc builds.  The 
respective executable file sizes are 20526 & 55148 bytes.

>You must use the same compiler to build & link.  ie you use gcc to 
>build the various code into .o files, you should use gcc to link the 
>.o files into an executable.
>[...]  gnu-ld is not supported for PAs running hpux.

Since gcc is just calling HP's ld, why do I have to link with gcc?  Is 
it automatically throwing in some linking options?

There are three things I'm still curious about:

1. Why isn't binutils' ld supported on HP-UX?

2. Why are my executable's sections reasonably close in size, but the 
executable files differ by more than 2.5x?

3.  How can I find out what routines are statically linked?  I know this 
may be an HP-UX question, but I can't figure it out.

Thanks.
--
John A. Breen
jab3@hotmail.com


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com