supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Charlie Brady <charlieb@e-smith.com>
Subject: How to cross-compile runit
Date: Tue, 13 Jan 2004 11:06:20 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0401131037060.20844-100000@allspice.nssg.mitel.com> (raw)


For those who might be interested, here's what's needed to be done to 
cross-compile runit. 

The Makefile as delivered assumes that it is possible to build binaries
and execute them in order to test for feature availability on the target.
You won't be able to do that in a cross compile environment. Instead, 
you'll need to do some hand testing to determine the correct answers to 
questions that make usually determines at build time.

# start with a clean slate
make clean

# Set up build tools
echo path/to/cc > conf-cc
echo path/to/cc -s > conf-ld

make compile load choose

# Detect and avoid imitation poll() libraries
# If trypoll builds and executes without error on the target
# set H to iopause.h2
H=iopause.h1
cp $H iopause.h

# Does target have 64bit long arithmetic?
# Test by building tryulong64 and executing on target
# set H to uint64.h2 if so
H=uint64.h1
cp $H uint64.h

# Does target have a short gid_t type?
# Test by building tryshsgr and executing on target
# set H to hasshsgr.h2 if so
make chkshsgr
H=hasshsgr.h1
cp $H hasshsgr.h

# All the configuration based on runtime results is now complete
# The rest are compile and/or link tests, and can be relied upon
make

--
Charlie



             reply	other threads:[~2004-01-13 16:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 16:06 Charlie Brady [this message]
2004-01-19 15:52 ` Clemens Fischer
2004-01-19 16:37   ` 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.44.0401131037060.20844-100000@allspice.nssg.mitel.com \
    --to=charlieb@e-smith.com \
    /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).