Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 111] New: binutils 2.17 fails to build when texinfo >= 4.10
Date: Wed, 18 Feb 2009 00:34:21 +0000 (UTC)	[thread overview]
Message-ID: <bug-111-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=111

              Host: openSESE 11.1
            Target: mipsel
             Build: 2009.02-rc4
           Summary: binutils 2.17 fails to build when texinfo >= 4.10
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Outdated package
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: luke_tucker at yahoo.co.uk
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


The configure script of binutils 2.17 tries to detect whether makeinfo is later
than v4.4 however it does not take into account minor versions with double
digits so v4.12 fails the test and stops binutils building even though the
texinfo verion is valid.


-- 
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.

             reply	other threads:[~2009-02-18  0:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18  0:34 bugzilla at busybox.net [this message]
2009-02-18  7:38 ` [Buildroot] [Bug 111] binutils 2.17 fails to build when texinfo >= 4.10 bugzilla at busybox.net
2009-03-03 21:24 ` bugzilla at busybox.net
2009-03-07 13:11 ` bugzilla at busybox.net

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=bug-111-163@https.bugs.busybox.net/ \
    --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