From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] minicom: add pre-configure hook to call autogen.sh
Date: Wed, 1 Aug 2018 16:48:52 +0200 [thread overview]
Message-ID: <20180801164852.7afe9c99@windsurf> (raw)
In-Reply-To: <20180801125721.34654-3-giulio.benetti@micronovasrl.com>
Hello,
On Wed, 1 Aug 2018 14:57:19 +0200, Giulio Benetti wrote:
> Using latest minicom git commit need to call autogen.sh instead of
> relying on Buildroot MINICOM_AUTORECONF = YES
>
> Add MINICOM_RUN_AUTOGEN to MINICOM_PRE_CONFIGURE_HOOKS and dependencies
> needed by autogen.sh like: host-automake, host-autoconf, host-libtool.
>
> Signed-off-by: Giulio Benetti <giulio.benetti@micronovasrl.com>
Looking at the autogen.sh script, I don't see anything fancy. What is
happening when you use MINICOM_AUTORECONF = YES ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-01 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 12:57 [Buildroot] [PATCH 0/4] minicom: update to use latest git repository Giulio Benetti
2018-08-01 12:57 ` [Buildroot] [PATCH 1/4] minicom: update package to use " Giulio Benetti
2018-08-01 12:57 ` [Buildroot] [PATCH 2/4] minicom: add pre-configure hook to call autogen.sh Giulio Benetti
2018-08-01 14:48 ` Thomas Petazzoni [this message]
2018-08-01 15:05 ` Giulio Benetti
2018-08-01 15:10 ` Thomas Petazzoni
2018-08-01 15:13 ` Giulio Benetti
2018-08-01 12:57 ` [Buildroot] [PATCH 3/4] minicom: delete patches Giulio Benetti
2018-08-01 12:57 ` [Buildroot] [PATCH 4/4] minicom: delete hash file Giulio Benetti
2018-08-01 14:47 ` [Buildroot] [PATCH 0/4] minicom: update to use latest git repository Thomas Petazzoni
2018-08-01 15:14 ` Giulio Benetti
2018-08-01 17:00 ` Thomas Petazzoni
2018-08-01 20:57 ` Giulio Benetti
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=20180801164852.7afe9c99@windsurf \
--to=thomas.petazzoni@bootlin.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 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.