From: John Long <codeblue@inbox.lv>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: Re: Error building from cvs
Date: Wed, 03 Jul 2013 17:17:00 -0000 [thread overview]
Message-ID: <20130703171740.GD18731@inbox.lv> (raw)
In-Reply-To: <51D44D16.3020805@redhat.com>
Thanks, I see you updated the CVS sources as well. This built fine and comes
up ok. I'll see what I can do with it!
/jl
On Wed, Jul 03, 2013 at 09:11:02AM -0700, Keith Seitz wrote:
> On 07/03/2013 04:06 AM, John Long wrote:
> >Can you please remind me how to apply your patches?
>
> Git format shouldn't matter: I apply those to branches all the time
> with `patch'. The probable cause is the leading path on that patch.
>
> The paths in the patch are all prefaced with: "a/gdb/gdbtk/generic"
> [or "b/gdb/gdbtk/generic"]. So depending on what source directory
> you are sitting in, you need to specify something other than "-p0"
> to `patch'.
>
> If the CWD is (from CVS) src/gdb/, then you need -p2. If the CWD is
> src/, you need -p1. If you are sitting in src/gdb/gdbtk/generic/,
> yes, you need -p4 to ignore the first for directory components in
> the patch.
>
> Keith
--
ASCII ribbon campaign ( ) Powered by Lemote Fuloong
against HTML e-mail X Loongson MIPS and OpenBSD
and proprietary / \ http://www.mutt.org
attachments / \ Code Blue or Go Home!
Encrypted email preferred PGP Key 2048R/DA65BC04
prev parent reply other threads:[~2013-07-03 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 9:42 John Long
2013-07-02 17:07 ` Keith Seitz
2013-07-02 17:48 ` John Long
2013-07-03 11:07 ` John Long
2013-07-03 16:11 ` Keith Seitz
2013-07-03 17:17 ` John Long [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=20130703171740.GD18731@inbox.lv \
--to=codeblue@inbox.lv \
--cc=insight@sourceware.org \
--cc=keiths@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).