From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: runit not ready for cross-compilation
Date: Tue, 3 Jan 2006 15:16:39 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.61.0601031508370.13430@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <200601032049.06956.radek@podgorny.cz>
On Tue, 3 Jan 2006, Radek Podgorny wrote:
> Well, let's get rid of all of this, then...
>
> In general there is no way to do runtime tests when building for different
> architecture. Are these tests even needed? No other software I know of
> doesn't do such things...
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.
Testing for available features and extant bugs this way is quick and
reliable. It just doesn't work for cross compilation.
Here's something for you to try:
make clean
make clean compile load choose
cat iopause.h1 > iopause.h
cat uint64.h1 > uint64.h
make chkshsgr
cat hasshsgr.h1 > hasshsgr.h
make
You might need to use h2 in place of h1, depending on your target. Mine is
little end MIPS.
next prev parent reply other threads:[~2006-01-03 20:16 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 [this message]
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=Pine.LNX.4.61.0601031508370.13430@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervision@budge.apana.org.au \
--cc=supervision@list.skarnet.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).