public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: David Bryson <mutex@gentoo.org>
To: Ned Ludd <solar@gentoo.org>
Cc: Mike Frysinger <vapier@gentoo.org>, gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] uclibc/busybox environment
Date: Sat, 9 Oct 2004 11:21:49 -0700	[thread overview]
Message-ID: <20041009182149.GA23886@heliosphan> (raw)
In-Reply-To: <1097344840.17568.25476.camel@simple>

[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]

On Sat, Oct 09, 2004 at 02:00:41PM -0400 or thereabouts, Ned Ludd wrote:
> 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.

Yes solar is right.
I originally submitted the embedded profile as an example of something
i hacked together.  I have a cascading one that isn't quite finished
yet, but hopefully in a week or so.
The point was to get *something* so that other people could see how
it's done, unfortunatly it has turned into bit rot.
In the next couple of weeks I'll post the profile and some patches for
catalyst that *really* help automation for embedded system building.


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-10-09 18:28 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
2004-10-09 18:21     ` David Bryson [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=20041009182149.GA23886@heliosphan \
    --to=mutex@gentoo.org \
    --cc=gentoo-embedded@lists.gentoo.org \
    --cc=solar@gentoo.org \
    --cc=vapier@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