Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Help needed with cross-compiling libotr
Date: Thu, 28 Feb 2013 12:43:09 -0300	[thread overview]
Message-ID: <512F7B0D.9020304@zacarias.com.ar> (raw)
In-Reply-To: <CAG2jQ8jiP6g7Fuhy_H3CgocC8CAMbT9ZF1sX22tsdOmyjhgsaQ@mail.gmail.com>

On 02/28/2013 12:36 PM, Markos Chandras wrote:
> I tend to agree that these kind of packages might be too much for
> buildroot, but keep in mind that Gentoo comes with a rather big uClibc
> rootfs by default [1]
> 
> [1] http://distfiles.gentoo.org/experimental/x86/uclibc/

A craftman would use catalyst to build his own stage(s) with a minimal
custom profile that gets rid of portage (thus ditching toolchain, python
and a ton other bloating things).
You could even use qmerge (portage-utils) to install extras if you
needed so.
Regards.

  parent reply	other threads:[~2013-02-28 15:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 15:04 [Buildroot] Help needed with cross-compiling libotr Stefan Fröberg
2013-02-28 15:06 ` Stefan Fröberg
2013-02-28 15:21 ` Thomas Petazzoni
2013-02-28 15:36   ` Markos Chandras
2013-02-28 15:43     ` Jeremy Rosen
2013-02-28 15:48       ` Thomas Petazzoni
2013-02-28 16:01         ` Stefan Fröberg
2013-02-28 15:43     ` Gustavo Zacarias [this message]
2013-02-28 15:49       ` Markos Chandras
2013-02-28 15:50         ` Thomas Petazzoni
2013-02-28 15:51           ` Gustavo Zacarias
2013-02-28 15:53           ` Markos Chandras
     [not found]   ` <512F7E8D.5070200@petroprogram.com>
2013-02-28 16:04     ` Stefan Fröberg

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=512F7B0D.9020304@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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