🚀 go-pugleaf

>I built two sets of object files using CC(1) for one, and
>gcc for the other. Now if I use the SUN-supplied ld to 
>link edit them like "ld  cc*.o gcc*.o", my executable
>is damaged (in my case, I received a Segmentation fault
>error).
>
>But if I use either "cc cc*.o gcc*.o" or "gcc cc*.o gcc*.o",
>the executable built will work. I certainly never ran into
>this problem before when all my object files are all built
>under one compiler. I wonder if you can shed some light
>on my puzzle, and also to my question, i.e. are GCC and
>sun's CC generate object files of the format ?

The problem is that when ld is invoked via cc or gcc, a number of additional
arguments are passed to it, such as crt0.o etc.  Because SunOS now supports
shared libraries and run-time dynamic linking, you do not see the result of
having incorrectly linked your executable until run time.  There is an
option to ld called -assert that is supposed to allow you to detect this
type of problem at link time; however, I have had limited success in using it.

--Marc Ullman
  Stanford University