From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: patch/list applied/ape-dumb-autohell-fixes
Date: Mon, 13 Feb 2006 12:44:14 -0800 [thread overview]
Message-ID: <43F0EF9E.4010301@orthanc.ca> (raw)
In-Reply-To: <43F0EAB8.3050504@lanl.gov>
> hmm. What uriel may be saying is that a lot of open source software,
> allegedly portable, is really only "portable" to different Linux
> distros. I have seen this more and more in recent years. Just take
> any of a dozen chunks of "portable" code and try to build it on mac
> osx, for example. All too often, if tails.
But you fairly quickly learn what these Linuxisms are, and how to undo
them. I own a Mac, and deal with this on a regular basis. Most of the
time I find the most non-portable part of the whole is
autoconf/configure. Somewhat ironic, don't you think? In my view,
autoconf has become a caricature of itself.
One reason why I like to keep a Solaris machine around is to have a
completely non-GNU compiler toolchain handy. That makes it easy to weed
this nonsense out. POSIX may be braindead in a lot of ways, but if used
with common sense it does allow for widely portable code. For the vast
majority of applications software, there really isn't any need for
autoconf in this day and age.
> It is also the case that some non-Linux OSes have felt pressure to
> add Linux-like features ...
Add? Or emulate. FreeBSD and Solaris both support runtime emulation of
Linux. This doesn't mean Linux is taking over the core OS (thank God).
I don't have a problem with anyone providing runtime ABI compatibility
for Linux applications, since it doesn't infect the core OS environment.
--lyndon
next prev parent reply other threads:[~2006-02-13 20:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7c5561c3fea402ccac05d5762e3d2aa7@plan9.bell-labs.com>
2006-02-13 16:17 ` uriel
2006-02-13 17:29 ` Russ Cox
2006-02-13 19:46 ` uriel
2006-02-13 15:19 ` Russ Cox
2006-02-13 19:51 ` Lyndon Nerenberg
2006-02-13 20:23 ` Ronald G Minnich
2006-02-13 20:44 ` Lyndon Nerenberg [this message]
2006-02-13 22:54 ` Ronald G Minnich
2006-02-14 15:57 ` David Leimbach
2006-02-13 20:21 ` Ronald G Minnich
2006-02-13 20:47 ` Steve Simon
2006-02-13 20:55 ` Paul Lalonde
2006-02-13 20:58 ` Steve Simon
2006-02-13 23:02 ` Ronald G Minnich
2006-02-13 21:07 ` andrey mirtchovski
2006-02-14 0:39 ` Latchesar Ionkov
2006-02-14 0:41 ` Paul Lalonde
2006-02-14 0:59 ` Latchesar Ionkov
2006-02-14 0:50 ` Joel Salomon
2006-02-14 0:53 ` Joel Salomon
2006-02-14 1:04 ` Latchesar Ionkov
2006-02-14 1:12 ` Joel Salomon
2006-02-14 9:47 ` Charles Forsyth
2006-02-14 11:37 ` Brantley Coile
2006-02-14 14:43 ` Ronald G Minnich
2006-02-14 10:12 ` Russ Cox
2006-02-14 15:10 ` Ronald G Minnich
2006-02-14 15:53 ` David Leimbach
2006-02-14 1:31 quanstro
2006-02-15 0:53 quanstro
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=43F0EF9E.4010301@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).