supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Gerrit Pape <pape@smarden.org>
Subject: Re: runit not ready for cross-compilation
Date: Tue, 3 Jan 2006 15:12:19 +0100	[thread overview]
Message-ID: <20060103141219.10168.qmail@b2e6e1223b0c20.315fe32.mid.smarden.org> (raw)
In-Reply-To: <200512120150.02803.radek@podgorny.cz>

On Mon, Dec 12, 2005 at 01:50:00AM +0100, Radek Podgorny wrote:
> The root of this problem is that you have to distinguish between host (build) 
> machine and target machine arch. Only single conf-cc and stuff simply isn't 
> enough. The same for ./compile script and so on.

Erm.  To me it doesn't make much sense to do runtime tests on the
build system for programs that actually will run on the target system.
Surely I may be wrong though.

Gerrit.


  parent reply	other threads:[~2006-01-03 14:12 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
2005-12-17 23:06       ` Charlie Brady
2005-12-18 10:30         ` Radek Podgorny
2006-01-03 14:12 ` Gerrit Pape [this message]
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=20060103141219.10168.qmail@b2e6e1223b0c20.315fe32.mid.smarden.org \
    --to=pape@smarden.org \
    /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).