From: "Peter S. Mazinger" <ps.m@gmx.net>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] dansguardian and uclibc++
Date: Wed, 28 Dec 2005 14:16:25 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0512281403260.21353-100000@lnx.bridge.intra> (raw)
In-Reply-To: <1135031031.20249.41.camel@nc>
On Mon, 19 Dec 2005, Natanael Copa wrote:
> On man, 2005-12-19 at 13:28 +0100, Peter S. Mazinger wrote:
> > On Fri, 16 Dec 2005, Natanael Copa wrote:
> >
> > > On tor, 2005-12-15 at 12:19 -0500, René Rhéaume wrote:
> > > > 2005/12/15, Natanael Copa <mlists@tanael.org>:
> > > > > I'm trying to avoid the gcc runtime dependency.
> > > > What do you mean ? libgcc or libstdc++ ?
> > >
> > > libstc++-v3 has like 23MB sources. It takes a while to compile.
> > > (Besides, it failed to compile.)
> > >
> > >
> > > # emerge -s libgcc
> > > Searching...
> > > [ Results for search key : libgcc ]
> > > [ Applications found : 0 ]
> > >
> > > libgcc? where can i find it?
> > >
> > > I would be much better if I could get it work with uclibc++. Its much
> > > smaller.
> > >
> > > I managed to get nmap to compile agains uclibc with
> > >
> > > CXX=g++-uc emerge nmap
> > >
> > > The romour says its possible to compile kde with uclibc++ so I was
> > > hoping it would be possible to use uclibc++
> > > -- > Natanael Copa
> >
> > the rumours are right, I have built the whole kde suite (emerge kde)
> > against uclibc++ (though not all uclibc++ related patches are in kde
> > upstream probably - these patches are general c++ failures mostly in kde,
> > not uclibc++ specific one, only libstdc++ tolerates some that are not
> > allowed by specs).
> >
> > I haven't done it your way though.
> > I have installed libuClibc++.so into the same dir where libstdc++.so sits,
> > I have created an include/uclibcxx for headers at same location as
> > include/g++-v3, I have created a new profile in /etc/env.d/gcc that uses
> > the same config as the gcc used to build libuClibc++. I have created a new
> > dir /usr/arch-*-uclibc/gcc-bin/<gcc-ver>-uclibcxx/ where every app is
> > symlinked to /usr/arch-*-uclibc/gcc-bin/<gcc-ver>/, the only change is
> > arch-*-linux-uclibc-c++, that is the uClibc++ wrapper
>
> Are you really sure that you mean "arch-*-linux-uclibc-c++" and not
> "arch-*-linux-uclibc-g++"? Or both?
both, g++ is a link to c++ in my
/etc/i386-gentoo-linux-uclibc/gcc-bin/3.4.5-uclibcxx/ dir
c++ is the wrapper
>
> When I like arch-*-linux-uclibc-c++ to g++-uc dansguardan gets compiled
> but it is still linked against libstdc++.so.6
well, then your wrapper/setup is somehow wrong. It would be "easier" if
an embedded dev would opt to add proper uClibc++ support to
toolchain.eclass maybe, we could build along libstdc++ uClibc++ too and
install both versions for !nocxx.
The only problem I encountered is that the you can have only one version
of uClibc++ installed, I tried slotting it (it should have the same
slotting as gcc), but the only way out of this missery is to add it too
the gcc pkg. What we also will encounter as problem is the
SPLIT_SPECS=true case, how do we then use libstdc++/uClibc++ switching
Maybe gcc-config/eselect* has to be improved to support changing the
underlaying uClibc++.
There would also be another way to do the setup:
soname libuClibc++.so.0 as libstdc++.so.0 and switch only the
libstdc++.so link from .so.[5,6] to libstdc++.so.0 or leave the soname as
it is and create libuClibc++.so libstdc++.so link. Then we do not need the
wrapper at all (the same has to happen with the include dir too, having
g++-v3 a link either to the gcc/libstdc++ version or the uclibc++ header
versions (STDCXX_INCDIR is ignored)
Peter
--
Peter S. Mazinger <ps dot m at gmx dot net> ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08 BB6E C389 975E A5F0 59F2
--
gentoo-embedded@gentoo.org mailing list
prev parent reply other threads:[~2005-12-28 13:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 17:01 [gentoo-embedded] dansguardian and uclibc++ Natanael Copa
2005-12-15 17:19 ` René Rhéaume
2005-12-16 7:52 ` Natanael Copa
2005-12-17 1:05 ` Ned Ludd
2005-12-19 10:33 ` [gentoo-embedded] uclibc++ as default for embedded (was: dansguardian and uclibc++) Natanael Copa
2005-12-19 12:33 ` [gentoo-embedded] dansguardian and uclibc++ Peter S. Mazinger
2005-12-20 7:55 ` Natanael Copa
2005-12-28 13:17 ` Peter S. Mazinger
2005-12-19 12:28 ` Peter S. Mazinger
2005-12-19 22:23 ` Natanael Copa
2005-12-28 13:16 ` Peter S. Mazinger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0512281403260.21353-100000@lnx.bridge.intra \
--to=ps.m@gmx.net \
--cc=gentoo-embedded@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox