From: Radek Podgorny <radek@podgorny.cz>
Subject: Re: runit not ready for cross-compilation
Date: Sat, 17 Dec 2005 23:58:04 +0100 [thread overview]
Message-ID: <200512172358.11513.radek@podgorny.cz> (raw)
In-Reply-To: <Pine.LNX.4.61.0512161031140.3689@e-smith.charlieb.ott.istop.com>
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
I though runit is a daemontools fork so we can give s... what djb thinks :-)
Are you gonna implement my cross-compilation stuff? Do want me anything to do
so you can actually do so?
Radek Podgorny
> On Sun, 11 Dec 2005, Alejandro Mery wrote:
> > yes, runit has the same bad habit djb software has. compiling it's own
> > build timers helpers in the same way that the runtime programs.
> >
> > what's the reason to use binary helpers instead of simple sh scripts for
> > those tasks?
>
> I think djb's rationale is that he can create his own portability, and
> doesn't depend on the portable implementation of features by the platform
> provider. Except for the compiler's C implementation, that is :-)
--
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x98E56D84
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-12-17 22:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 0:50 Radek Podgorny
2005-12-12 2:21 ` Alejandro Mery
2005-12-16 15:33 ` Charlie Brady
2005-12-17 22:58 ` Radek Podgorny [this message]
2005-12-17 23:06 ` Charlie Brady
2005-12-18 10:30 ` Radek Podgorny
2006-01-03 14:12 ` Gerrit Pape
2006-01-03 19:49 ` Radek Podgorny
2006-01-03 20:16 ` Charlie Brady
2006-01-05 15:01 ` Charles Duffy
2006-01-05 15:17 ` Charlie Brady
2006-01-06 3:54 ` Alejandro Mery
2006-01-06 11:07 ` Radek Podgorny
2006-01-06 12:51 ` Charles Duffy
2006-01-06 13:54 ` OT: cross compilation and autoconf [was: Re: runit not ready for cross-compilation] Charles Duffy
2006-01-06 16:54 ` Laurent Bercot
2006-01-06 18:42 ` Charlie Brady
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=200512172358.11513.radek@podgorny.cz \
--to=radek@podgorny.cz \
/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).