On Mon, Nov 17, 2008 at 7:17 PM, Jesper Skov <[email protected]> wrote: > On Sun, Nov 16, 2008 at 9:46 PM, Andrew Lunn <[email protected]> wrote: >> On Sun, Nov 16, 2008 at 03:40:12PM +0100, Jesper Skov wrote: >>> Hi >>> >>> BSD/OS X does not provide a static implementation of libsupc++.a. So >>> my attempted port of the synthetic target to BSD is limping badly. >> >> I synthetic port to BSD/OS X sounds interesting. How similar are the >> system calls? Can you just write a i386bsd, or do you have to modify >> the HAL arch as well? > > I only cloned the platform folder. It wasn't too hard to make eCos work. > > The biggest problem is with the toolchain, really, as the GNU tools > have not been > ported to OS X (or maybe BSD in general, I don't know). > > I'll try to post some source to the patches list this week or next, to get > some > feedback on the changes. I'll also get started on a copyright assignment with > gnu.org.
As should be evident, "this week or next" has not come by yet. I have had the occasional stab at the linker problems I am experiencing with the Mac tools without getting any further. Basically, handling of C++ constructors is (as far as I can figure out) handled by the dynamic linker used with the MachO file format. So the constructor code is not "loaded". Which makes it rather hard to call after eCos gets started. I have tried to let the dynamic linker call the constructors, but never got it to work. Not sure why. And I am now fresh out of ideas. So I will try to post patches with the stuff I have made (probably earlyish in the new year). Anyone wanting to use it on an ELF-based BSD system will probably be able to use most of it without problems. I have sent copyright assignment stuff to FSF, but never heard back. I guess I will have to resend. Not how I had hoped this would play out. Oh well... :) Cheers, Jesper -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
