From: Pascal de Bruijn <pmjdebruijn@gmail.com>
Subject: runit (1.0.5)
Date: Tue, 11 Jul 2006 16:12:49 +0200 [thread overview]
Message-ID: <1152627169.11798.22.camel@localhost> (raw)
Hi,
I noticed runit, which looks really great! I intend to use it on my
homebuilt embedded linux os, which runs on a PC-Engines WRAP board
(which are low powered x86 compatible boards).
I'm using buildroot/uclibc to build the embedded os. This is where the
trouble starts. buildroot more or less expects a standard autoconf
structure or at least something similar. And your build scripts don't
seem to allow for certain build parameters:
--target=$(GNU_TARGET_NAME)
--host=$(GNU_TARGET_NAME)
--build=$(GNU_HOST_NAME)
There build parameters are necessary because my compiler isn't called
just 'gcc' but 'i486-linux-gcc'. I'm basically cross compiling on the
from and to the same platform, because I don't want to rely on my
distribution supplied compiler.
Is there any convenient way to make this work?
Regards,
Pascal de Bruijn
--
http://blog.pcode.nl/
http://del.icio.us/pmjdebruijn/
http://www.flickr.com/photos/pmjdebruijn/
next reply other threads:[~2006-07-11 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 14:12 Pascal de Bruijn [this message]
2006-07-12 15:16 ` Gerrit Pape
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=1152627169.11798.22.camel@localhost \
--to=pmjdebruijn@gmail.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).