From: Laurent Bercot <ska-supervision@skarnet.org>
Subject: Re: OT: cross compilation and autoconf [was: Re: runit not ready for cross-compilation]
Date: Fri, 6 Jan 2006 17:54:35 +0100 [thread overview]
Message-ID: <20060106165435.GA11832@skarnet.org> (raw)
In-Reply-To: <dplsre$h80$1@sea.gmane.org>
> Additionally, it's better to have something that's *consistent* and
> written to make cross compilation reasonably straightforward than for
> every package to have its own custom configure/build system
Yes. That's why it's best to have ONE custom configure/build system
designed once and for all. :)
If you're experienced in portability problems, could you please check
out the configuration scripts in skalibs (derived from DJB scripts,
but more complete) and tell me if there's some obvious sysdep that I
have forgotten ?
The beast is at http://www.skarnet.org/software/skalibs/
and I use it to avoid EVER having to learn or rely on autoconf.
Thanks for your kind help. :)
--
Laurent
next prev parent reply other threads:[~2006-01-06 16:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 0:50 runit not ready for cross-compilation 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
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 [this message]
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=20060106165435.GA11832@skarnet.org \
--to=ska-supervision@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).