From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Binutils: ARC: Fix build failures if makeinfo is missing
Date: Mon, 06 Jun 2016 23:34:53 +0200 [thread overview]
Message-ID: <87fusqgfwi.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20160606215833.57396ae8@free-electrons.com> (Thomas Petazzoni's message of "Mon, 6 Jun 2016 21:58:33 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Hello,
> On Mon, 06 Jun 2016 21:36:54 +0200, Peter Korsgaard wrote:
>> > Signed-off-by: Zakharov Vlad <vzakhar@synopsys.com>
>>
>> Committed, thanks.
> Why?
It was fixing autobuilder issues and seemed like a sensible fix that
could be upstreamed. Looking again, I do see that it patched Makefile.in
and not Makefile.am, so that's not too nice though.
> This problem also exists for other versions of binutils, and also for
> gdb. And we have a patch series from Romain Naour sitting in patchwork
> for several weeks.
> I don't know if Zlad's version is better or not than Romain's version.
> But at least Romain's version was handling all binutils and gdb
> versions, without patching directly Makefile.in files. So at first
> sight, it looked a lot better than Zlad's version.
Ok, we can always revert if it isn't needed any more once Romain's
series is applied.
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-06-06 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 11:14 [Buildroot] [PATCH] Binutils: ARC: Fix build failures if makeinfo is missing Zakharov Vlad
2016-06-06 19:36 ` Peter Korsgaard
2016-06-06 19:58 ` Thomas Petazzoni
2016-06-06 21:34 ` Peter Korsgaard [this message]
2016-06-07 5:42 ` Alexey Brodkin
2016-06-15 17:18 ` Alexey Brodkin
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=87fusqgfwi.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.