From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/974 Path: news.gmane.org!not-for-mail From: Charlie Brady Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: runit not ready for cross-compilation Date: Thu, 5 Jan 2006 10:17:53 -0500 (EST) Message-ID: References: <200512120150.02803.radek@podgorny.cz> <20060103141219.10168.qmail@b2e6e1223b0c20.315fe32.mid.smarden.org> <200601032049.06956.radek@podgorny.cz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Trace: sea.gmane.org 1136474281 17640 80.91.229.2 (5 Jan 2006 15:18:01 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 5 Jan 2006 15:18:01 +0000 (UTC) Original-X-From: supervision-return-1210-gcsg-supervision=m.gmane.org@list.skarnet.org Thu Jan 05 16:17:59 2006 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1EuWsJ-00035n-7n for gcsg-supervision@gmane.org; Thu, 05 Jan 2006 16:17:59 +0100 Original-Received: (qmail 29671 invoked by uid 76); 5 Jan 2006 15:18:17 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 29665 invoked from network); 5 Jan 2006 15:18:17 -0000 X-X-Sender: charlieb@e-smith.charlieb.ott.istop.com Original-To: supervision@list.skarnet.org In-Reply-To: Xref: news.gmane.org gmane.comp.sysutils.supervision.general:974 Archived-At: On Thu, 5 Jan 2006, Charles Duffy wrote: > Charlie Brady wrote: >> As has earlier been pointed out, other software does do such >> compile-link-run testing - most or all of Dan Bernstein's software does >> it, as does software derived from Dan's software. I think you'll also >> find that some software configured via ./configure will also do such >> tests, just not as explicitly. > > Autoconf, however, has provisions for cross-compiling: Sure, and sometimes it's broken. And always it's overcomplicated. > The packager can specify test results for the given target ... Which is essentially what I'm doing. > via environment variables; defaults can be provided for use in > cross-compilation environments; and as many tests as possible are done > *without* requiring the use of a target-compiled binary. But let's not talk too much about autoconf. Would anyone care to comment about my workaround? Is it "good enough" (so that the build system doesn't need to be rewritten)? Would someone care to document the correct h1/h2 choices for various platforms?