Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Khem Raj <kraj@mvista.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Convert VALUE_EMBEDDED_OFFSET to function
Date: Tue, 08 Feb 2005 22:33:00 -0000	[thread overview]
Message-ID: <42087C6D.3010603@mvista.com> (raw)
In-Reply-To: <42084932.8070505@gnu.org>

Hi Andrew,

I did a fresh checkout  now I am getting an error at  different place  
during make install.

Thanks
Khem
 
makeinfo --split-size=5000000 -I 
../../../../src/gdb/doc/../../readline/doc -I 
../../../../src/gdb/doc/../mi -I ../../../../src/gdb/doc \
        -o gdb.info ../../../../src/gdb/doc/gdb.texinfo
../../../../src/gdb/doc/gdb.texinfo:7035: warning: @strong{Note:} 
produces a spurious cross-reference in Info; reword to avoid that.
../../../../src/gdb/doc/gdb.texinfo:21102: @dots expected braces.
../../../../src/gdb/doc/gdb.texinfo:21102: @- missing close brace.
makeinfo: Removing output file `gdb.info' due to errors; use --force to 
preserve.
make[3]: *** [gdb.info] Error 1
make[3]: Leaving directory `/root/sourceware/objdir/gdb-obj/gdb/doc'


Andrew Cagney wrote:

> Khem Raj wrote:
>
>> Hi Andrew
>>
>> I am getting error building gdb and I think if following change 
>> should also be part of your changeset.
>
>
> GDB builds.
>
> It looks like you've done something like "cvs update -d" which picks 
> up some extra directories.  I'd make a clean-sweep of things and try 
> again with a clean checkout.
>
> Andrew


  reply	other threads:[~2005-02-08  8:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 21:48 Andrew Cagney
2005-02-08  2:02 ` Khem Raj
2005-02-08 21:03   ` Andrew Cagney
2005-02-08 22:33     ` Khem Raj [this message]
2005-02-08  5:08 ` Khem Raj

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=42087C6D.3010603@mvista.com \
    --to=kraj@mvista.com \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@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