Xref: utzoo comp.realtime:1162 gnu.g++.help:474
Path: utzoo!utgpu!watserv1!watmath!uunet!shelby!snorkelwacker.mit.edu!mintaka!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!spool.mu.edu!sol.ctr.columbia.edu!emory!stiatl!srchtec.searchtech.com!monica
From: monica@srchtec.uucp (Monica Skidmore)
Newsgroups: comp.realtime,gnu.g++.help
Subject: Re: initialization with g++ and vxWorks
Keywords: g++,vxWorks
Message-ID: <1991Feb14.180721.28794@srchtec.uucp>
Date: 14 Feb 91 18:07:21 GMT
References: <1991Feb11.034536.10212@xavax.com>
Organization: search technology, inc.
Lines: 19

In article <1991Feb11.034536.10212@xavax.com> jat@xavax.com (John Tamplin) writes:
>You really should use gnu-ld -- without collect.  gnu-ld just collects the
>list of static constructors and destructors for you -- the functions
>to actually create and destroy these objects are called from main().
>g++ inserts the code into your main routine.  If vxWorks arranges to
>call main for you, you are all set once you use gnu-ld to do your final
>link.  If you are doing the final link under vxWorks, you will need to
>run collect over the output.

We have tried to use collect, but we are having trouble getting it to
compile on our SUN 3.  There are several macros which should expand to 
assembly language which are undefined.  Does anyone know how we should 
define these macros?

-- 
----
Monica D. Skidmore                            monica@searchtech.com
search technology, inc.                       emory!stiatl!srchtec!monica
Atlanta, Georgia                              monica@srchtec.uucp