All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] undefined macro: AM_PROG_LIBTOOL (buildroot failure)
Date: Fri, 13 Jun 2008 10:49:50 +0200	[thread overview]
Message-ID: <87k5gtyb0x.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <6306c640805281409v1bf5384ag2c1353fd4aead298@mail.gmail.com> (Ram kumar's message of "Thu\, 29 May 2008 02\:39\:28 +0530")

>>>>> "Ram" == Ram kumar <ramkumar.research@gmail.com> writes:

 Ram> hi,

 Ram>      Iam trying to build a development environment using
 Ram> buildroot for my atmel eval kit (AT91SAM9260 ek).I follow the
 Ram> instruaction in the website http://
 Ram> www.linux4sam.org/twiki/bin/view/Linux4SAM/BuildRoot. But my
 Ram> buildroot fails when it is trying to build libusb.

 Ram> First the buildroot throws 404 file not found error since
 Ram> http://ftp.debian.org /pool/main/libu/libusb/ doesn't have
 Ram> libusb_0.1.12-9.diff.gz which buildroot looks for......so i
 Ram> edited the /buildroot/package/libusb/libusb.mk file to download
 Ram> libusb_0.1.12-11.diff.gz which is present in the FTP server.

libusb missed a dependency on host-libtool and patch version bumped.
Fixed in r22311-r22313.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2008-06-13  8:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 21:09 [Buildroot] undefined macro: AM_PROG_LIBTOOL (buildroot failure) Ram kumar
2008-06-13  8:49 ` Peter Korsgaard [this message]
2008-09-25 10:52   ` Ram kumar
2008-09-29  9:53     ` Peter Korsgaard
2008-09-25 10:54   ` Ram kumar

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=87k5gtyb0x.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.