From: Charles Duffy <cduffy@spamcop.net>
Subject: Re: runit not ready for cross-compilation
Date: Thu, 05 Jan 2006 09:01:40 -0600 [thread overview]
Message-ID: <dpjcck$a8p$1@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0601031508370.13430@e-smith.charlieb.ott.istop.com>
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: The packager can
specify test results for the given target 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.
next prev parent reply other threads:[~2006-01-05 15:01 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
2006-01-03 19:49 ` Radek Podgorny
2006-01-03 20:16 ` Charlie Brady
2006-01-05 15:01 ` Charles Duffy [this message]
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='dpjcck$a8p$1@sea.gmane.org' \
--to=cduffy@spamcop.net \
/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).