From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Gnu/Stallman (was Bugs in V6 'dcheck')
Date: Mon, 2 Jun 2014 12:44:46 -0600 [thread overview]
Message-ID: <0336AA23-2BB0-4ACE-80DC-570B2A32F19E@bsdimp.com> (raw)
In-Reply-To: <20140602173521.GX18282@mercury.ccil.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1534 bytes --]
On Jun 2, 2014, at 11:35 AM, John Cowan <cowan at mercury.ccil.org> wrote:
> arnold at skeeve.com scripsit:
>
>
>> This is only possible because of the standardization efforts at the
>> C and POSIX levels. Remember that Autoconf/Automake were invented to
>> solve the issue of all the forks: SunOS / Solaris / HP-UX / Ultrix /
>> MIPS / Pryamid / DG-UX / ad nauseum. Lots of things that were almost but
>> not quite entirely like V7 or System V Unix.
>
> Oh, absolutely. But Autotools themselves are very unstable, so we've
> apparently replaced spatial variation with longitudinal variation.
> The Chicken project was undergoing too much churn trying to run correctly
> with different installed versions of Autotools. So we switched to CMake,
> but that was even more unstable, and couldn't handle a bootstrapped
> self-compiler well.
>
> So finally we switched to the current scheme of Makefile fragments.
> Each fragment specifies appropriate cc and ld options, including libraries
> required, and then writes out a chicken-defaults.h file with a bunch of
> HAVE_* macros. That's all that's needed.
Sounds a bit like imake-uberlite… Or should I not mention imake lest the love-fest for all things evil continue on it. :)
Warner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20140602/08a4544b/attachment.sig>
next prev parent reply other threads:[~2014-06-02 18:44 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 2:09 Doug McIlroy
2014-06-02 2:24 ` John Cowan
2014-06-02 2:59 ` Warner Losh
2014-06-02 3:17 ` Greg 'groggy' Lehey
2014-06-02 3:37 ` John Cowan
2014-06-02 4:08 ` scj
2014-06-02 5:03 ` Greg 'groggy' Lehey
2014-06-02 12:31 ` Ronald Natalie
2014-06-02 4:04 ` Nick Downing
2014-06-02 4:43 ` John Cowan
2014-06-02 6:23 ` arnold
2014-06-02 17:35 ` John Cowan
2014-06-02 18:44 ` Warner Losh [this message]
2014-06-02 18:52 ` John Cowan
2014-06-02 3:18 ` John Cowan
2014-06-02 6:08 ` Steve Nickolas
2014-06-02 12:04 ` Clem Cole
2014-06-02 12:27 ` Ronald Natalie
2014-06-02 13:28 ` Clem Cole
2014-06-02 14:11 ` Tim Bradshaw
2014-06-02 14:25 ` Clem Cole
2014-06-02 14:41 ` John Cowan
2014-06-02 14:50 ` Armando Stettner
2014-06-02 18:27 ` Brantley Coile
2014-06-02 18:52 ` Dan Cross
2014-06-02 19:10 ` arnold
2014-06-03 1:45 ` Brantley Coile
2014-06-02 19:30 ` John Cowan
2014-06-02 19:54 ` Dan Cross
2014-06-02 23:37 ` John Cowan
2014-06-03 1:24 ` Dan Cross
2014-06-03 2:16 ` John Cowan
2014-06-03 2:18 ` Dan Cross
2014-06-02 19:47 ` Chris Nehren
2014-06-02 20:23 ` Dan Cross
2014-06-03 18:48 ` [TUHS] Evolutionary Paths (was Gnu/Stallman (was Bugs in V6 'dcheck')) scj
2014-06-04 1:10 ` Larry McVoy
2014-06-04 3:42 ` Greg Chesson
2014-06-05 0:43 ` Larry McVoy
2014-06-02 21:08 ` [TUHS] Gnu/Stallman (was Bugs in V6 'dcheck') Charlie Kester
2014-06-03 0:37 ` Tim Newsham
2014-06-02 20:06 ` Jacob Goense
2014-06-02 14:26 ` arnold
2014-06-02 14:30 ` John Cowan
2014-06-02 14:24 ` John Cowan
2014-06-02 14:29 ` Ronald Natalie
2014-06-02 14:37 ` Clem Cole
2014-06-05 7:31 ` Arno Griffioen
2014-06-05 8:24 ` emu
2014-06-05 9:17 ` Wesley Parish
2014-06-05 11:26 ` Brantley Coile
2014-06-05 13:34 ` Jesus Cea
2014-06-11 12:10 ` Michael Parson
2014-06-12 1:20 ` Wesley Parish
2014-06-05 15:07 ` Clem Cole
2014-06-05 18:26 ` Ronald Natalie
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=0336AA23-2BB0-4ACE-80DC-570B2A32F19E@bsdimp.com \
--to=imp@bsdimp.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 NNTP newsgroup(s).