1 |
Hi, |
2 |
|
3 |
I have been using crossdev and gentoo to build an uclibc embedded platform |
4 |
with great successes so far. My toolchain is built using: |
5 |
|
6 |
crossdev -binutils 2.16.1-r2 -gcc 3.4.5-r1 -libc 0.9.29 -kernel 2.6.16.20 -t |
7 |
i386-pc-linux-uclibc |
8 |
|
9 |
and |
10 |
|
11 |
crossdev -binutils 2.16.1-r2 -gcc 3.4.5-r1 -libc 0.9.29 -kernel 2.6.16.20 -t |
12 |
arm-softfloat-linux-uclibc |
13 |
|
14 |
As you can see I am targeting both Intel and Arm platforms. I'm using a |
15 |
portage snapshot from portage-20060703.tar.gz. I intend only to update the |
16 |
portage snapshot I am using only if I need to to fix a bug or add features. |
17 |
|
18 |
I need to run C++ code. I have managed to build C++ apps ok linked against |
19 |
libstdc++ and all appears to run OK. On investigating some problems though I |
20 |
have found that on the Intel platform at least (I will find out soon if this |
21 |
occurs on the ARM platform) when an exception is thrown by C++ code Abort is |
22 |
called and the exception is not handled correctly. I can get a stack trace |
23 |
if it might help anyone. |
24 |
|
25 |
My question is if anyone has come across this problem before? If so if they |
26 |
are aware of a fix? Can anyone confirm a portage snapshot and crossdev |
27 |
command line(the versions) they use to build a uclibc toolchain in which |
28 |
they know C++ exceptions to be working? |
29 |
|
30 |
I will research the problem and if I find a solution will post it here. |
31 |
Thanks in advance for help. |
32 |
|
33 |
Ryan |