public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sander Knopper <sander@knopper.tk>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] uclibc/busybox environment
Date: Sat, 9 Oct 2004 20:14:18 +0200	[thread overview]
Message-ID: <200410092014.18983.sander@knopper.tk> (raw)
In-Reply-To: <1097344840.17568.25476.camel@simple>

Op zaterdag 9 oktober 2004 20:00, schreef Ned Ludd:
> On Sat, 2004-10-09 at 13:25, Mike Frysinger wrote:
> > On Saturday 09 October 2004 06:50 am, Sander Knopper wrote:
> > > Is there a way to combine these two profiles or is it better to make
> > > one of my own? At the moment I would go with the second option since it
> > > would allow me to use busybox, uclibc and also give me the opportunity
> > > to leave utilities as gawk, grep, gzip and tar away because busybox
> > > already supplies them. I'll have to take the fact that these programs
> > > sometimes aren't fully compatible with their GNU relatives for granted.
> >
> > the idea was to use uclibc for development systems and embedded for the
> > target (i think, solar can correct me)
> >
> > ive been keeping the uclibc profile up-to-date, but i think the embedded
> > one could use some work ...
>
> Indeed the embedded one could. I've mentioned this one to Chris before
> about it using glibc vs uclibc by default on IRC but I think he was in
> the middle of his work day. That profile was added long before we had a
> pretty decent uClibc native environments setup so a instantaneous switch
> might not be possible or we could break some existing users setups.
>
> But as I see things it stands right now the embedded profile target
> could be split up into glibc/uclibc subsystems. We could use these
> profiles for our vendor mini distros like soekris, wrt54g's. netwinders,
> nslu2, video systems, pbx systems, kiosk, dumb terminals, etc..
> However those profiles would have to be based on user/vendor submissions
> as our gentoo devs only provocatively support what we have hardware for.
> donations welcome be that time or hardware or documentation to help ease
> this maze of what we call embedded.
>
> But so far not a lot of effort has been put into this area of profiles
> because there has been lots of hurdles for us to overcome in the process
> of the development environment alone.

At the moment I've combined the two profiles, it seems to work at my computer. 
The most difficult part though, is to delete perl and some other packages. 
Especially since autoconf/automake and some other packages depend on it 
because of the wrapper. Currently I'm trying to overcome this by modifying 
some ebuilds and put them in portage-overlay but it's not very clean though.

I'm also thinking of just dropping automake/autoconf...;) The only packages 
that seems to depend on it is libtool and this is due to some bugs which I've 
to take a closer look at.

--
gentoo-embedded@gentoo.org mailing list


  reply	other threads:[~2004-10-09 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-09 10:50 [gentoo-embedded] uclibc/busybox environment Sander Knopper
2004-10-09 17:25 ` Mike Frysinger
2004-10-09 18:00   ` Ned Ludd
2004-10-09 18:14     ` Sander Knopper [this message]
2004-10-09 18:21     ` David Bryson

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=200410092014.18983.sander@knopper.tk \
    --to=sander@knopper.tk \
    --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