1 |
On man, 2005-12-19 at 13:28 +0100, Peter S. Mazinger wrote: |
2 |
> On Fri, 16 Dec 2005, Natanael Copa wrote: |
3 |
> |
4 |
> > On tor, 2005-12-15 at 12:19 -0500, René Rhéaume wrote: |
5 |
> > > 2005/12/15, Natanael Copa <mlists@××××××.org>: |
6 |
> > > > I'm trying to avoid the gcc runtime dependency. |
7 |
> > > What do you mean ? libgcc or libstdc++ ? |
8 |
> > |
9 |
> > libstc++-v3 has like 23MB sources. It takes a while to compile. |
10 |
> > (Besides, it failed to compile.) |
11 |
> > |
12 |
> > |
13 |
> > # emerge -s libgcc |
14 |
> > Searching... |
15 |
> > [ Results for search key : libgcc ] |
16 |
> > [ Applications found : 0 ] |
17 |
> > |
18 |
> > libgcc? where can i find it? |
19 |
> > |
20 |
> > I would be much better if I could get it work with uclibc++. Its much |
21 |
> > smaller. |
22 |
> > |
23 |
> > I managed to get nmap to compile agains uclibc with |
24 |
> > |
25 |
> > CXX=g++-uc emerge nmap |
26 |
> > |
27 |
> > The romour says its possible to compile kde with uclibc++ so I was |
28 |
> > hoping it would be possible to use uclibc++ |
29 |
> > -- > Natanael Copa |
30 |
> |
31 |
> the rumours are right, I have built the whole kde suite (emerge kde) |
32 |
> against uclibc++ (though not all uclibc++ related patches are in kde |
33 |
> upstream probably - these patches are general c++ failures mostly in kde, |
34 |
> not uclibc++ specific one, only libstdc++ tolerates some that are not |
35 |
> allowed by specs). |
36 |
> |
37 |
> I haven't done it your way though. |
38 |
> I have installed libuClibc++.so into the same dir where libstdc++.so sits, |
39 |
> I have created an include/uclibcxx for headers at same location as |
40 |
> include/g++-v3, I have created a new profile in /etc/env.d/gcc that uses |
41 |
> the same config as the gcc used to build libuClibc++. I have created a new |
42 |
> dir /usr/arch-*-uclibc/gcc-bin/<gcc-ver>-uclibcxx/ where every app is |
43 |
> symlinked to /usr/arch-*-uclibc/gcc-bin/<gcc-ver>/, the only change is |
44 |
> arch-*-linux-uclibc-c++, that is the uClibc++ wrapper |
45 |
|
46 |
Are you really sure that you mean "arch-*-linux-uclibc-c++" and not |
47 |
"arch-*-linux-uclibc-g++"? Or both? |
48 |
|
49 |
When I like arch-*-linux-uclibc-c++ to g++-uc dansguardan gets compiled |
50 |
but it is still linked against libstdc++.so.6 |
51 |
|
52 |
> in /etc/env.d/gcc/ I have copied the config of used build gcc to |
53 |
> arch-*-linux-uclibc-<gcc-ver>-uclibcxx and replaced |
54 |
> PATH/ROOTPATH/STDCXX_INCDIR w/ new locations (STDCXX_INCDIR is useless, |
55 |
> don't rely on that, because it is not used -correctly-, you have to use |
56 |
> the correct path in the wrapper) |
57 |
> Now I can switch w/ gcc-config to the profile using uclibc++ as with any |
58 |
> other gcc one. |
59 |
> Currently it is heavily dependant on the gcc version used to build |
60 |
> uClibc++, don't try to use it w/ other gcc. |
61 |
> |
62 |
> Peter |
63 |
> |
64 |
> -- |
65 |
> Peter S. Mazinger <ps dot m at gmx dot net> ID: 0xA5F059F2 |
66 |
> Key fingerprint = 92A4 31E1 56BC 3D5A 2D08 BB6E C389 975E A5F0 59F2 |
67 |
> |
68 |
|
69 |
-- |
70 |
gentoo-embedded@g.o mailing list |