All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 161] New: vim fails on patching with errors in configure.patch
Date: Mon,  9 Mar 2009 17:13:41 +0000 (UTC)	[thread overview]
Message-ID: <bug-161-163@https.bugs.busybox.net/> (raw)

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

           Summary: vim fails on patching with errors in configure.patch
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: igor47 at moomers.org
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


1 out of 423 hunks FAILED -- saving rejects to file src/auto/configure.rej
Patch failed!  Please fix configure.patch!
make: *** [/provisioning/buildroot/buildroot-2009.02/build_i686/vim71/.patched]
Error 1

the earlier error is:
misordered hunks! output would be garbled
Hunk #399 FAILED at 14947.

removing that hunk from the patch file only causes additional errors.
i couldn't fix this, but after the error simply touch vim71/.patched and
continuing on with the make seems to be a usable workaround.


-- 
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-03-09 17:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09 17:13 bugzilla at busybox.net [this message]
2009-03-09 19:48 ` [Buildroot] [Bug 161] vim fails on patching with errors in configure.patch 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-161-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 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.