Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Ray Duran" <Ray.Duran@FutureElectronics.com>
To: "Joel Brobecker" <brobecker@adacore.com>
Cc: <gdb@sourceware.org>
Subject: RE: gdb build error
Date: Tue, 19 Sep 2006 17:54:00 -0000	[thread overview]
Message-ID: <3CE39F664D1EE14293F6923CD00E42C705DDFF47@montremsg32.na.future.ca> (raw)

Joel,

Is there a good site that you know of where I can get a download where I
will not have 
this problem?

Thanks,

-Ray

-----Original Message-----
From: Joel Brobecker [mailto:brobecker@adacore.com] 
Sent: Tuesday, September 19, 2006 10:53 AM
To: Ray Duran
Cc: gdb@sourceware.org
Subject: Re: gdb build error


> I looked at the tarball after "untaring" file and I cannot see
> ada-lex.c.  Where can I find an insight tarball that I can build gdb(
> with ada-lex.c)

That's the problem - the tarball should include that file.
What you need to do is to tell the people who created that tarball
to make sure that ada-lex.c is included.

Or perhaps it was an intentional decision on their part. This file
is not part of the CVS tree, but is automatically created during
the GDB release creation process.

-- 
Joel


             reply	other threads:[~2006-09-19 17:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19 17:54 Ray Duran [this message]
2006-09-19 17:59 ` Joel Brobecker
2006-09-19 18:00   ` Daniel Jacobowitz
2006-09-19 18:54   ` Keith Seitz
  -- strict thread matches above, loose matches on Subject: below --
2006-09-19 21:38 Ray Duran
2006-09-19 17:49 Ray Duran
2006-09-19 17:52 ` Joel Brobecker
2006-09-19 19:07   ` Michael Snyder
2006-09-07 17:43 Ray Duran
2006-09-07 17:41 Ray Duran
2006-09-19  5:37 ` Joel Brobecker
2006-09-06 22:40 Ray Duran
2006-09-07 16:15 ` Joel Brobecker
2006-09-06 22:01 Ray Duran
2006-09-06 22:06 ` Joel Brobecker
2006-09-06 22:10   ` Daniel Jacobowitz
2006-09-06 22:14     ` Mark Kettenis
2006-09-06 22:18     ` Joel Brobecker

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=3CE39F664D1EE14293F6923CD00E42C705DDFF47@montremsg32.na.future.ca \
    --to=ray.duran@futureelectronics.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    /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