From: niky <b4506051@csie.ntu.edu.tw>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: how to apply the patches for i386
Date: Wed, 29 Nov 2000 19:04:00 -0000 [thread overview]
Message-ID: <200011300304.LAA26871@ntucst.csie.ntu.edu.tw> (raw)
Hi,
After I applied the perl script to the patch, there are some problems
from the patchs. I checked out the packages from anoncvs.
patching file hal/i386/arch/current/src/vectors.S
Hunk #7 FAILED at 228.
1 out of 9 hunks FAILED -- saving rejects to file
hal/i386/arch/current/src/vectors.S.rej
...
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n] y
Hunk #1 FAILED at 65.
Hunk #2 FAILED at 92.
Hunk #3 FAILED at 155.
Hunk #4 FAILED at 170.
Hunk #5 succeeded at 198 (offset -11 lines).
Hunk #6 succeeded at 332 (offset 3 lines).
Hunk #7 succeeded at 402 (offset -11 lines).
Hunk #8 succeeded at 438 (offset 3 lines).
4 out of 8 hunks FAILED -- saving rejects to file
...
What can I do ?
Thanks.
next reply other threads:[~2000-11-29 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 19:04 niky [this message]
2000-11-30 2:07 ` Robin Farine
2000-12-03 4:30 niky
2000-12-04 12:07 Fabrice Gautier
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=200011300304.LAA26871@ntucst.csie.ntu.edu.tw \
--to=b4506051@csie.ntu.edu.tw \
--cc=ecos-discuss@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).