From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fakeroot: bump version to 1.21-2
Date: Mon, 13 Mar 2017 13:32:20 +0100 [thread overview]
Message-ID: <20170313133220.62892a21@free-electrons.com> (raw)
In-Reply-To: <d5b7097f-1af5-1130-21b2-fb3c1278a646@andin.de>
Hello,
On Mon, 13 Mar 2017 11:43:49 +0100, Andreas Naumann wrote:
> I have another reason to bump to 1.21, but experience the same
> difficulties in getting the configure step right. What would be a
> sensible way to avoid depending on autoconf/automake?
Is your reason to depend on automake/autoconf still the same as what it
was in Maxime's patch? If so, then we can patch Makefile.in instead of
Makefile.am. We normally don't like that very much, but I personally
prefer this solution over having fakeroot depending on
automake/autoconf.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-13 12:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 11:53 [Buildroot] [PATCH] fakeroot: bump version to 1.21-2 Maxime Hadjinlian
2016-10-04 14:35 ` Thomas Petazzoni
2016-10-04 14:39 ` Maxime Hadjinlian
2017-03-13 10:43 ` Andreas Naumann
2017-03-13 12:32 ` Thomas Petazzoni [this message]
2017-03-13 15:23 ` Andreas Naumann
2017-03-13 16:33 ` Yann E. MORIN
2017-03-14 8:16 ` Thomas Petazzoni
2017-03-14 11:04 ` Andreas Naumann
2017-03-14 13:48 ` Andreas Naumann
2017-03-15 0:20 ` Arnout Vandecappelle
2017-03-15 8:17 ` Andreas Naumann
2017-03-15 19:07 ` Arnout Vandecappelle
2017-03-15 19:46 ` Arnout Vandecappelle
2017-03-15 20:09 ` Yann E. MORIN
2017-03-15 20:41 ` Peter Korsgaard
2017-03-15 22:35 ` Thomas Petazzoni
2017-03-15 22:55 ` Peter Korsgaard
2017-03-16 8:13 ` Andreas Naumann
2017-03-16 22:39 ` Arnout Vandecappelle
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=20170313133220.62892a21@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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