From: Peter Stuge <peter@stuge.se>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] ref bug 297229 (virutal/libiconv vs sys-libs/uclibc[iconv] vs sys-devel/gcc)
Date: Fri, 4 Jun 2010 17:56:21 +0200 [thread overview]
Message-ID: <20100604155621.18483.qmail@stuge.se> (raw)
In-Reply-To: <4C08E724.3080605@wildgooses.com>
Ed W wrote:
> I'm still not sure I understand why I don't just do this "properly"
> and either use iconv in uclibc or libiconv (and gettext)?
Is it big? Is it neccessary? Usually it's a high priority to take
away every last thing that is not absolutely neccessary.
//Peter
next prev parent reply other threads:[~2010-06-04 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 10:42 [gentoo-embedded] ref bug 297229 (virutal/libiconv vs sys-libs/uclibc[iconv] vs sys-devel/gcc) Ed W
2010-06-03 23:02 ` Ned Ludd
2010-06-04 11:44 ` Ed W
2010-06-04 15:56 ` Peter Stuge [this message]
2010-06-04 23:20 ` solar
2010-06-07 10:20 ` Ed W
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=20100604155621.18483.qmail@stuge.se \
--to=peter@stuge.se \
--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