Xref: utzoo gnu.g++:1108 comp.realtime:886 Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!uw-beaver!fluke!kelpie From: kelpie@tc.fluke.COM (Tony Garland) Newsgroups: gnu.g++,comp.realtime Subject: Re: configuring g++ for VxWorks Summary: VxWorks User's Group, software and information sharing Message-ID: <1990Sep13.153820.24310@tc.fluke.COM> Date: 13 Sep 90 15:38:20 GMT References: Distribution: usa Organization: John Fluke Mfg. Co., Inc., Everett, WA Lines: 82 In article , tsai@venus.ral.rpi.edu (Jodi Tsai) writes: > I'm looking for a way to have g++ setup so that it can cross compile > C++ code for VxWorks. I've tried doing it myself, but I'm not sure > how to handle the intialization of global constructors which I assume > is being done in crt1+.c, I would appreciate any information > including newsgroups, mailing lists, or ftp sites on how to get g++ > properly configured for VxWorks. > I am working in the same direction with VxWorks and have found the VxWorks User's Group to be of much value. Others are successfully working using g++ with VxWorks (and you probably know that VxWorks will be releasing a remote debugger based upon gdb soon). The user's group operates through a voluntary central archival location using a mail robot. Much of the software deals with ANSIfying VxWorks, making it work with g++, and some useful class examples (prioritized pipes, counting semaphores, etc.). This includes code supporting the builtin operators new and delete. Here's the scoop: | To get the basic information to get you started, send an email message | to the address: | | vxworks_archive@ncar.ucar.edu | | The subject can anything, but the body of the message must be: | | send index | | This will cause the server to email you the base index and help guide | for the server. Here's more info: |From: sypko@rtsg.ee.lbl.gov (Sypko Andreae) |Subject: UPD_900904: vxwexplo.msg |To: bradf@tekig3.pen.tek.com, lewin@sanders.com, hikashi@arisia.Xerox.COM, | rfg@ncd.com, blewett@research.att.com, kcooley@teknowledge.com, | schuld@ibm.com, warb@gvlv2.gvl.unisys.com, vxwexplore@gandalf.ca, | rau@sj.ATE.SLB.COM, lacy@draper.com, | sandra@digigw.lab.nanko.digital.co.jp, kelpie@tc.fluke.COM, | grahamd@otc.otca.oz.au, bernard@vesuve.cge.fr, mea@sparta.com, | rec@mpl.ucsd.edu |Cc: sypko@rtsg.ee.lbl.gov | |Dear future VxWorks Exploder user: | |This message serves to check if we can reach you with |the return address supplied in your request message. | |Please acknowledge receipt of this message. |Within about a week of your return message your |e-mail address will be added to the list. | |In your acknowledge message please give us your voice phone |and FAX number, your mailing address and your affiliation, if |you have not done so already. | |To use the VXWEXPLO (exploder) to broadcast a message to |all 150+ people/institutions on the list, simply e-mail to | | vxwexplo @ lbl.gov | |The VxWorks Archive is maintained by Richard Neitzel (303) 497-2057, |thor@thor.atd.ucar.EDU. This archive contains an assortment of |public domain vxworks/unix code. The messages to this exploder |are also archived there by the month. To contact the archive's |email server send a message containing the text 'send index' to | | vxworks_archive @ ncar.ucar.EDU | |Richard Neitzel should be contacted regarding the archive email robot. | |Let me know if you have any problems with the exploder. | | Sypko Andreae, UCLBL, (415) 486-7531 | UCLBL, Mailstop 46A, Berkeley, CA 94720 | e-mail: sypko@rtsg.ee.lbl.gov | |