From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: cygwin-talk@cygwin.com
Subject: Re: ELIX?
Date: Fri, 09 Oct 2009 20:43:00 -0000 [thread overview]
Message-ID: <4ACFA3E5.40703@gmail.com> (raw)
In-Reply-To: <20091009202915.GB30037@ednor.casa.cgf.cx>
Christopher Faylor wrote:
> On Fri, Oct 09, 2009 at 09:10:22PM +0100, Dave Korn wrote:
>> Christopher Faylor wrote:
>>> On Fri, Oct 09, 2009 at 11:33:22AM -0600, Morgan Gangwere wrote:
>>>> On Fri, Oct 9, 2009 at 11:20 AM, Richard Campbell <ulvester@yahoo!> wrote:
>>>>> Can anyone give me an explanation (or just a link, google is not
>>>>> helping me) to what ELIX is (as in the ELIX level 2, ELIX level 4
>>>>> defines and guards in newlib)?
>>>> It vaguely appears on the horizon as something thats used by redhat
>>>> under Newlib -- apparently its a check-bound system?
>>> IIRC, elix was an early aborted foray into an embedded version of linux
>>> which used newlib as its libc. I remember it being mentioned a lot when
>>> I was at Cygnus/Red Hat and then, as with many projects at Red Hat,
>>> vanishing with a *poof*.
>> Not /entirely/ vanished:
>>
>> http://sourceware.org/elix/
>>
>> ... but not updated in a looong time.
>
> Well, no. It obviously didn't entirely vanish or people wouldn't be
> asking why it was in newlib.
>
> I asked Jeff Johnston if I could delete it from newlib once and he
> told me that it still had some use. I don't remember what that was
> though.
Yeh, I remember that thread. I never knew there was a homepage and a spec
document kicking around though.
cheers,
DaveK
prev parent reply other threads:[~2009-10-09 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 17:21 ELIX? Richard Campbell
2009-10-09 17:33 ` ELIX? Morgan Gangwere
2009-10-09 18:24 ` ELIX? Christopher Faylor
2009-10-09 19:55 ` ELIX? Dave Korn
2009-10-09 20:29 ` ELIX? Christopher Faylor
2009-10-09 20:43 ` Dave Korn [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=4ACFA3E5.40703@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=cygwin-talk@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).