C++ support in DSLINUX
amadeus at iksw-muees.de
Sun Oct 15 13:33:48 CEST 2006
I think this is a mojor place of work now...
I have used the rtest program (user/rtest) to have a simple c++ test
I have ironed out the correct placement of the C++ include directories
in the common config.arch file, and I have included the c++ libs for
the linker in ucfront.c.
Now it's possible to compile C++ programs with $CXX $CXXFLAGS
and link C++ programs with $CXX.
But if you want to run the programs, I have noted the following
a) a C++ program, only main and no c++ features, will load and run.
b) a C++ program, using classes, will load, but gives a "data abort" at
address 0x1d. (rtest)
c) a C++ program, using iostream, will not load - relocation out of
Some other notes:
- omitting the -fpic flags will not work in the RAM/RAMDEVEL build,
because there is a code generator error which is not fixed. hmmmpf.
- trying to use shared libs does not work.
- if I compile and link rtest, in the code there are references to strb,
which comes out of the c++ compiler libs. So there is a toolchain build
problem with the multilibs and mswp-byte-writes.
Ruling from the number of postings to mailing lists, c++ support in
uCLinux is a problem by itself. I was not able to find a toolchain
which claims to _work_ for all special cases (pic, multilib, flat).
So I think we have to iron this out with our current environment.
Anybody care to help? This is getting tough.
We're back to the times when men were men
and wrote their own device drivers.
More information about the dslinux-devel