From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-06-08
Date: Wed, 11 Jun 2014 10:56:53 +0200 [thread overview]
Message-ID: <20140611105653.4e25ec3c@free-electrons.com> (raw)
In-Reply-To: <20140609211036.GA10459@ned>
Dear Eric Le Bihan,
On Mon, 9 Jun 2014 23:10:36 +0200, Eric Le Bihan wrote:
> - We are stuck with autoreconf, as it is needed to solve the `ln --relative`
> issue via a patch, which will not be accepted by upstream [8].
If we're stuck with autoreconf due to a patch that will not be accepted
upstream, then I would suggest that we move away from autoreconf, and
turn this patch into something that changes Makefile.in and configure
directly, with a good explanation in the patch description.
Hopefully, ln implementations in distributions will be upgraded, and at
some time, we'll be able to drop the patch.
The drawback with this solution is that if we want to create/backport
other systemd patches that require autoreconf, then we're screwed. So
maybe carrying our copy of libgcrypt.m4 as a patch in systemd sources is
the easiest solution here.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-11 8:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-06-08 Thomas Petazzoni
2014-06-09 10:07 ` Yann E. MORIN
2014-06-09 10:11 ` Thomas Petazzoni
2014-06-09 10:15 ` Yann E. MORIN
2014-06-09 12:04 ` François Perrad
2014-06-09 12:19 ` Yann E. MORIN
2014-06-09 21:10 ` Eric Le Bihan
2014-06-11 8:56 ` Thomas Petazzoni [this message]
2014-06-11 21:04 ` Eric Le Bihan
2014-06-11 21:13 ` Yann E. MORIN
2014-06-11 21:47 ` Eric Le Bihan
2014-06-11 21:54 ` Yann E. MORIN
2014-06-12 7:08 ` Thomas Petazzoni
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=20140611105653.4e25ec3c@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