From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] gdb: get rid of host-texinfo dependency
Date: Sun, 9 Oct 2016 15:04:51 +0200 [thread overview]
Message-ID: <20161009150451.404e6641@free-electrons.com> (raw)
In-Reply-To: <20161009135552.5dd553fe@free-electrons.com>
Hello,
On Sun, 9 Oct 2016 13:55:52 +0200, Thomas Petazzoni wrote:
> All three patches applied to master. Thanks!
And I reverted the texinfo patch and the binutils patch. The binutils
patch badly breaks the build of the toolchain. See:
http://autobuild.buildroot.net/results/90d/90d0537bc12cbb2a7c6d344b3c6c9e1a5046d791/build-end.log
http://autobuild.buildroot.net/results/9a2/9a2b30bfd08c3a4af43f0523276eb5f799699aaa/build-end.log
http://autobuild.buildroot.net/results/d8a/d8a4afeeec8d6b070b17a067d0ded5aefe4e3f6a/build-end.log
Please do a toolchain build before sending the next iterations of the
patches. A basic ARM toolchain would not even build with your
patches :-/
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-09 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 19:03 [Buildroot] [PATCH v2 1/3] gdb: get rid of host-texinfo dependency Thomas De Schampheleire
2016-10-08 19:03 ` [Buildroot] [PATCH v2 2/3] binutils: get rid of host-texinfo dependency and other documentation tricks Thomas De Schampheleire
2016-10-08 19:03 ` [Buildroot] [PATCH v2 3/3] Revert "texinfo: new host package" Thomas De Schampheleire
2016-10-09 11:55 ` [Buildroot] [PATCH v2 1/3] gdb: get rid of host-texinfo dependency Thomas Petazzoni
2016-10-09 13:04 ` Thomas Petazzoni [this message]
2016-10-09 13:13 ` Thomas De Schampheleire
2016-10-09 14:32 ` Waldemar Brodkorb
2016-10-09 18:44 ` Thomas De Schampheleire
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=20161009150451.404e6641@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