From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 111] binutils 2.17 fails to build when texinfo >= 4.10
Date: Sat, 7 Mar 2009 13:11:04 +0000 (UTC) [thread overview]
Message-ID: <20090307131104.65ADE76525@busybox.osuosl.org> (raw)
In-Reply-To: <bug-111-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=111
--- Comment #3 from Luke <luke_tucker@yahoo.co.uk> 2009-03-07 13:11:03 UTC ---
The reason I was using binutils 2.17 is because I'm building applications for a
reverse engineered platform (TViX DVICO 6500) and I am trying to keep
everything as close to the toolchain used by the original developers even
though 2.19 will probably work as you say.
Thanks for the fix.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
prev parent reply other threads:[~2009-03-07 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 0:34 [Buildroot] [Bug 111] New: binutils 2.17 fails to build when texinfo >= 4.10 bugzilla at busybox.net
2009-02-18 7:38 ` [Buildroot] [Bug 111] " bugzilla at busybox.net
2009-03-03 21:24 ` bugzilla at busybox.net
2009-03-07 13:11 ` bugzilla at busybox.net [this message]
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=20090307131104.65ADE76525@busybox.osuosl.org \
--to=bugzilla@busybox.net \
--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