public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Natanael Copa <mlists@tanael.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] dansguardian and uclibc++
Date: Mon, 19 Dec 2005 23:23:51 +0100	[thread overview]
Message-ID: <1135031031.20249.41.camel@nc> (raw)
In-Reply-To: <Pine.LNX.4.44.0512191309190.32286-100000@lnx.bridge.intra>

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?

When I like arch-*-linux-uclibc-c++ to g++-uc dansguardan gets compiled
but it is still linked against libstdc++.so.6

> in /etc/env.d/gcc/ I have copied the config of used build gcc to 
> arch-*-linux-uclibc-<gcc-ver>-uclibcxx and replaced 
> PATH/ROOTPATH/STDCXX_INCDIR w/ new locations (STDCXX_INCDIR is useless, 
> don't rely on that, because it is not used -correctly-, you have to use 
> the correct path in the wrapper)
> Now I can switch w/ gcc-config to the profile using uclibc++ as with any 
> other gcc one.
> Currently it is heavily dependant on the gcc version used to build 
> uClibc++, don't try to use it w/ other gcc.
> 
> 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



  reply	other threads:[~2005-12-19 22:25 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 [this message]
2005-12-28 13:16         ` Peter S. Mazinger

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=1135031031.20249.41.camel@nc \
    --to=mlists@tanael.org \
    --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