From: Isaac Dunham <idunham-N9AOi2cAC9ZBDgjK7y7TUQ@public.gmane.org>
To: toybox-oU9gvf+ajcRUPo+8YfT7LV6hYfS7NtTn@public.gmane.org
Cc: musl-ZwoEplunGu1jrUoiu81ncdBPR1lH4CV8@public.gmane.org
Subject: Re: [musl] Re: toybox: Rough edges in pending
Date: Tue, 19 Mar 2013 12:32:21 -0700 [thread overview]
Message-ID: <20130319123221.ddd8eb53.idunham@lavabit.com> (raw)
In-Reply-To: <1363713627.15703.33@driftwood>
On Tue, 19 Mar 2013 12:20:27 -0500
Rob Landley <rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org> wrote:
> On 03/19/2013 01:50:43 AM, Isaac Dunham wrote:
> > Hello,
> > I don't expect these to be very high priority, but I ran into a few
> > rough edges
> > when enabling almost all the toys in pending:
>
> Um, yes. Until recently half the stuff in pending didn't even
> _compile_. There's a _reason_ the default to 'n'. It's a directory full
> of things that people are unhappy if I keep out of tree (usually for
> months), but which aren't ready to be used either.
I knew it was "unsupported" but didn't realize it was expected to be quite that bad. I assumed (yes, I know the saying...) that if find,
uu{en,de}code, xzcat, and stat seemed to be functional in my testing, the other parts might also.
A couple things that would have cleared this up for me--
Either a note in toys/pending/README that said:
"Code in this directory may or may not work." (somehow, "...await review and/or cleanup" doesn't seem to communicate this)
or a "CONFIG_WORKING" that prevents enabling toys that are nonfunctional without realizing it (iirc, the kernel has a trick along these lines, so make allyesconfig doesn't turn _everything_ on).
But please leave pending in.
> > Also, when toybox is built with musl, and toybox sh executes ls,
> > I get a hang; strace indicates that something funny is going on:
>
> I am honestly amazed it got _that_ far.
>
> > I anticipate this is a bug in musl, so I'll cross-post.
>
> If toysh _isn't_ corrupting the heap or something similar, I'd be
> stunned. It's not a real command yet.
Surprisingly enough, it makes it far enough to give the illusion it might be usable.
--
Isaac Dunham <idunham-N9AOi2cAC9ZBDgjK7y7TUQ@public.gmane.org>
next prev parent reply other threads:[~2013-03-19 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 6:50 Isaac Dunham
2013-03-19 9:42 ` Szabolcs Nagy
2013-03-19 11:09 ` Szabolcs Nagy
[not found] ` <20130319110939.GJ19010-4P1ElwuDYu6sTnJN9+BGXg@public.gmane.org>
2013-03-19 17:33 ` [musl] " Rob Landley
2013-03-19 17:20 ` [Toybox] " Rob Landley
2013-03-19 19:32 ` Isaac Dunham [this message]
2013-03-20 6:22 ` [Toybox] [musl] " Rob Landley
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=20130319123221.ddd8eb53.idunham@lavabit.com \
--to=idunham-n9aoi2cac9zbdgjk7y7tuq@public.gmane.org \
--cc=musl-ZwoEplunGu1jrUoiu81ncdBPR1lH4CV8@public.gmane.org \
--cc=toybox-oU9gvf+ajcRUPo+8YfT7LV6hYfS7NtTn@public.gmane.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).