supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Alejandro Mery <amery@geeks.cl>
Subject: Re: runit not ready for cross-compilation
Date: Sun, 11 Dec 2005 23:21:17 -0300	[thread overview]
Message-ID: <439CDE9D.6090204@geeks.cl> (raw)
In-Reply-To: <200512120150.02803.radek@podgorny.cz>

Radek Podgorny wrote:
> Hi,
> 
> I'm trying to make runit run on my arm-based PDA. There's a problem that I 
> have to cross-compile runit on my i686 host and it doesn't work. To be more 
> specific, it works until the point where it tries to run some compiled 
> program...

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?

Alejandro Mery


  reply	other threads:[~2005-12-12  2:21 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 [this message]
2005-12-16 15:33   ` Charlie Brady
2005-12-17 22:58     ` Radek Podgorny
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=439CDE9D.6090204@geeks.cl \
    --to=amery@geeks.cl \
    /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).