mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: compatability: heirloom-utils +.5, libarchive -1
Date: Wed, 4 Jan 2012 18:05:26 -0800	[thread overview]
Message-ID: <20120104180526.05c071fe@newbook> (raw)
In-Reply-To: <20120103173808.GH14961@port70.net>

On Tue, 3 Jan 2012 18:38:08 +0100
Szabolcs Nagy <nsz@port70.net> wrote:
> i had to fix things in heirloom to be able to compile
> it with pcc+musl
> i did about the same hacks, but then i ran various tests
> and some of the more obscure tools failed so i figured
> heirloom is not that good quality, eg.:
> nl -b a -v 0
> (i would never use nl but it turns out the build
> script mess of dash does ..for whatever reason)
heirloom toolchest has about four "personalities":
1. SVRx (default?)
2. BSD
3. Single UNIX 3
4. SUS
(The latter two are variants of POSIX)
In general, the POSIX variants are about as close to precisely
standards-conformant as you can get; unfortunately, the plain old UNIX
versions are default. I note, though, that nl presumably ought to start
numbering at 0 when specified; instead, it starts at 1 (SU3/SUS
variants), skipping the line that would be numbered 0.  The old unix
version apparently didn't recognize -b.
But I figure it beats Busybox any day--and I'd rather not use GNU
bloat.

I'd rather use mksh/ksh93, but if you want a POSIX shell, the Bourne
shell beats dash on standards-conformance (after all, it *is* the
standard). mksh (when invoked as sh) is almost pure POSIX.

Isaac



  reply	other threads:[~2012-01-05  2:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 14:06 Isaac Dunham
2012-01-03 17:38 ` Szabolcs Nagy
2012-01-05  2:05   ` Isaac Dunham [this message]
2012-01-06  8:41     ` Rich Felker
2012-01-06 14:08       ` Szabolcs Nagy
2012-01-07  1:38       ` Isaac Dunham
2012-01-03 17:49 ` Rich Felker

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=20120104180526.05c071fe@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).