Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] macro `AM_PROG_LIBTOOL' not found
Date: Fri, 13 Jun 2008 15:54:07 +1000	[thread overview]
Message-ID: <20080613055407.GA26459@cloud.net.au> (raw)
In-Reply-To: <484EDB38.8030308@acsatlanta.com>

On Tue, Jun 10, 2008 at 02:51:20PM -0500, Joseph G. Boike wrote:
> Hi,
> I'm trying to cross compile buildroot for and Atmel at91sam9260 ARM 
> processor and keep getting the same error below.
> I started w/ a clean buildroot subdirectory and used the default make 
> (make at91sam9260_defconfig) setup.
> My native autoconf, automake and libtool are all in /usr/bin
> The error references m4_pattern_allow.  Where do I add that?  How do I 
> keep it if I get a new version of buildroot?

Thanks, I fixed it now in svn (r22311).

libusb.mk should probably be rewritten to use the autotools stuff.

Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

  reply	other threads:[~2008-06-13  5:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 19:51 [Buildroot] macro `AM_PROG_LIBTOOL' not found Joseph G. Boike
2008-06-13  5:54 ` Hamish Moffatt [this message]
2008-06-13  8:48 ` Peter Korsgaard

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=20080613055407.GA26459@cloud.net.au \
    --to=hamish@cloud.net.au \
    --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