mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: gcc segfault at src/mman/mlockall.c
Date: Fri, 18 May 2012 17:45:33 -0700	[thread overview]
Message-ID: <20120518174533.22b8c9e2@newbook> (raw)
In-Reply-To: <20120518225845.GY163@brightrain.aerifal.cx>

On Fri, 18 May 2012 18:58:45 -0400
Rich Felker <dalias@aerifal.cx> wrote:
> > On Fri, May 18, 2012 at 08:43:33PM +0200, Jens Staal wrote:
> > > > obase-musl still lacks a lot due to many legacy syscalls musl
> > > > probably won't implement.
> > > >
> > > Could libbsd help with those?
..
> There's really no cost to adding syscall
> wrappers. If it's a matter of library functions though, then yes, I'd
> agree. If using obase is desirable, it would be best to patch out the
> non-portable stuff in obase, or if that's too difficult, use libbsd
> (hopefully an improved version; in its current form, it seems very
> broken and like gnulib has a lot of #error in the #else cases).
I ought to try compiling libbsd again...
 
> By the way, sbase in its current form is not much of an option. As far
> as I can tell, the only way its tools "suck less" is in the area of
> bloat; in the area of actually working correctly, they leave A LOT to
> be desired. For example, at a first glance, grep lacks support for
> multiple regexes (either on the command line with -e or
> newline-separated, or from a file with -f). This kind of
> non-conformance will badly break all sorts of shell scripts, including
> possibly configure scripts (thus making it impossible to build any
> software).
> 
> There is also my noXCUse package, which aims at complete conformance
> in all commands implemented, but not many commands are implemented
> yet.
Had not heard of that one, and Google seems not to recognize it... Is it
publicly available yet?

While we're enumerating permissively-licensed userspaces, we might as
well remember Android's toolbox, and more relevantly toybox (Landley's
project that set off the whole discussion of licensing).
And in the less-viable set of options, there's beastiebox (way too
limited and BSD-specific, though it may compile on Linux),
and somewhere I saw a git repo with a port of netbsd userspace to
uclibc (incompatible with musl, of course--uclibc seems to be the most
"legacy friendly" libc in terms of headers, even compared with glibc).
Besides that there's heirloom-tools.
That would make 8 packages under permissive licenses that aim at what
you're talking about.
So it isn't like there's a lack of options, it's just that none of
them seem to be ready at present.
By the way, make is probably one of the biggest limitations--Linux and
musl both rely extensively on gmake features that none of the
BSD/permissively-licensd make versions support yet.  You probably won't
get the kernel policy changed, either.

Isaac Dunham



  parent reply	other threads:[~2012-05-19  0:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 16:35 Isaac Dunham
2012-05-15 16:42 ` Isaac Dunham
2012-05-15 19:21   ` Szabolcs Nagy
2012-05-15 19:30     ` Szabolcs Nagy
2012-05-16 18:53       ` Isaac Dunham
2012-05-16 22:04         ` Szabolcs Nagy
2012-05-17  6:07           ` Isaac Dunham
2012-05-18 14:58           ` Jens Staal
2012-05-18 17:21             ` Christian Neukirchen
2012-05-18 18:43               ` Jens Staal
2012-05-18 18:51                 ` Kurt H Maier
2012-05-18 22:58                   ` Rich Felker
2012-05-18 23:13                     ` Kurt H Maier
2012-05-19  0:45                     ` Isaac Dunham [this message]
2012-05-19  0:56                       ` Rich Felker
2012-05-19 18:45                         ` noXCUse, userspace options Isaac Dunham
2012-05-24  6:16                         ` noXCUse grep Isaac Dunham
2012-05-19 21:26                     ` gcc segfault at src/mman/mlockall.c Christian Neukirchen

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=20120518174533.22b8c9e2@newbook \
    --to=idunham@lavabit.com \
    --cc=musl@lists.openwall.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.
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).