Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Replace libev with libuv
Date: Fri, 18 Jul 2014 17:26:00 -0300	[thread overview]
Message-ID: <53C982D8.7070006@zacarias.com.ar> (raw)
In-Reply-To: <CALoSW6550gT0qvqgo2tbaz+_VKXy0mwAQxjmsjPV66-XaUC1VA@mail.gmail.com>

On 07/18/2014 11:02 AM, Nimai Mahajan wrote:

>>>> libuv v0.11.25 Autoreconfiguring
> aclocal: error: configure.ac:18: file
> 'm4/libuv-extra-automake-flags.m4' does not exist
> autoreconf: /home/user/Desktop/buildroot-2014.02/output/host/usr/bin/aclocal
> failed with exit status: 1
> make: *** [/home/user/Desktop/buildroot-2014.02/output/build/libuv-v0.11.25/.stamp_configured]
> Error 1
> 
> The problem is its not running the autogen.sh. How do I force this to
> run? Is the only way still through <PKG_NAME>_POST_EXTRACT_HOOKS or
> <PKG_NAME>_POST_PATCH_HOOKS?

I've just sent a patch to the list to add libuv.
Basically autogen.sh is doing a dirty deed, so i've added that in a
POST_PATCH_HOOK instead of running autogen.sh - we really want to avoid
doing so as much as possible.
Regards.

  reply	other threads:[~2014-07-18 20:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 12:48 [Buildroot] Replace libev with libuv Nimai Mahajan
2014-07-18 13:12 ` Gustavo Zacarias
     [not found]   ` <CALoSW64Uisj3oLvPVKZ1nQXgCTEnt1yLMqV+Gy7aK4U=Q9FcUA@mail.gmail.com>
2014-07-18 13:32     ` Gustavo Zacarias
2014-07-18 14:02       ` Nimai Mahajan
2014-07-18 20:26         ` Gustavo Zacarias [this message]
2014-07-18 23:36         ` Nimai Mahajan
2014-07-19 12:42           ` Nimai Mahajan
2014-07-19 13:18             ` Yann E. MORIN
2014-07-19 12:51           ` Nimai Mahajan
2014-07-19 13:20             ` Yann E. MORIN
2014-07-19 13:40               ` Nimai Mahajan
2014-07-19 23:12                 ` Yann E. MORIN

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=53C982D8.7070006@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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