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 593] New: Missing early check for patch(1)
Date: Fri,  4 Sep 2009 18:22:59 +0000 (UTC)	[thread overview]
Message-ID: <bug-593-163@https.bugs.busybox.net/> (raw)

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

           Summary: Missing early check for patch(1)
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: felix.nawothnig at drdannenberg.de
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


I'm preparing a tool-chain inside a fresh virtual machine and although the
process pretty quickly informed me about the missing bison and flex binaries it
was just when it was trying to patch the kernel sources (I believe) when it
realized I didn't have a patch binary installed.

I realize you might never early-check all dependencies for what-ever weird
configuration options the user might have chosen, but as this is a pretty basic
one I'm filing this as an enhancement.


-- 
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-09-04 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-04 18:22 bugzilla at busybox.net [this message]
2009-10-25 21:16 ` [Buildroot] [Bug 593] Missing early check for patch(1) 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-593-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