Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/autoconf
Date: Thu, 29 Jan 2009 07:15:37 +0100	[thread overview]
Message-ID: <20090129071537.5f22f517@hcegtvedt> (raw)
In-Reply-To: <873af3v3ru.fsf@macbook.be.48ers.dk>

On Wed, 28 Jan 2009 16:39:17 +0100
Peter Korsgaard <jacmet@uclibc.org> wrote:

> >>>>> "laird" == laird  <laird@uclibc.org> writes:
> 
>  laird> Author: laird
>  laird> Date: 2009-01-28 15:35:39 +0000 (Wed, 28 Jan 2009)
>  laird> New Revision: 25102
> 
>  laird> Log:
>  laird> autoconf.mk: Bounce version to 2.63
> 
>  laird> Have been having various issues with multiple jobs (-jX) and
>  laird> building autoconf.  Turns out that v2.63 has fixed this.  So
>  laird> bounce version to a working version.
> 
> Ok, let's give it a good shake to see if anything breaks with this.
> 

Please note that autoconf 2.63 is not compatible with autoconf 2.61, at
least from my experience. So I say all packages should be configured
and built to test if this is working as expected.

And since we're already touching autoconf, install it to
toolchain_build_ARCH/bin as well? (-:

-- 
Best regards,
Hans-Christian Egtvedt

  reply	other threads:[~2009-01-29  6:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 15:35 [Buildroot] svn commit: trunk/buildroot/package/autoconf laird at uclibc.org
2009-01-28 15:39 ` Peter Korsgaard
2009-01-29  6:15   ` Hans-Christian Egtvedt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-03 13:36 tpetazzoni at uclibc.org
2007-01-29 12:51 aldot at uclibc.org
2007-01-10 18:39 aldot at uclibc.org

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=20090129071537.5f22f517@hcegtvedt \
    --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