From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] start compiling autoconf for the host as well (was: svn commit: trunk/buildroot/package/autoconf)
Date: Wed, 03 Dec 2008 14:43:37 +0100 [thread overview]
Message-ID: <49368D09.6060703@atmel.com> (raw)
In-Reply-To: <20081203133645.EBECF3C83E@busybox.net>
tpetazzoni at uclibc.org wrote:
> Author: tpetazzoni
> Date: 2008-12-03 05:36:45 -0800 (Wed, 03 Dec 2008)
> New Revision: 24242
>
> Log:
> Fix comment about autoconf configuration/compilation/installation for
> the target (and not the host).
>
off-topic: perhaps we should consider building autoconf, libtools, etc.
which now quite heavily depend on when cross-compiling. I.e. not all
distributions ship 2.13 and 2.61. AFAIK Gentoo uses 2.63.
--
Best regards,
Hans-Christian Egtvedt
next prev parent reply other threads:[~2008-12-03 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 13:36 [Buildroot] svn commit: trunk/buildroot/package/autoconf tpetazzoni at uclibc.org
2008-12-03 13:43 ` Hans-Christian Egtvedt [this message]
2008-12-03 15:34 ` [Buildroot] start compiling autoconf for the host as well (was: svn commit: trunk/buildroot/package/autoconf) Thomas Petazzoni
2008-12-04 6:33 ` Hans-Christian Egtvedt
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=49368D09.6060703@atmel.com \
--to=hans-christian.egtvedt@atmel.com \
--cc=buildroot@busybox.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