From: "Ray Duran" <Ray.Duran@FutureElectronics.com>
To: "Michael Snyder" <Michael.Snyder@palmsource.com>,
"Joel Brobecker" <brobecker@adacore.com>
Cc: <gdb@sourceware.org>
Subject: RE: gdb build error
Date: Tue, 19 Sep 2006 21:38:00 -0000 [thread overview]
Message-ID: <3CE39F664D1EE14293F6923CD00E42C704CD96B3@montremsg32.na.future.ca> (raw)
Thank you very much Michael for your explanation.
I will try both options; Copying file from gdb release
and using flex.
Thanks again.
-Ray
-----Original Message-----
From: Michael Snyder [mailto:Michael.Snyder@palmsource.com]
Sent: Tuesday, September 19, 2006 12:07 PM
To: Joel Brobecker; Ray Duran
Cc: gdb@sourceware.org
Subject: RE: gdb build error
Ray, here's your problem in a nutshell:
ada-lex.c is not a "primary source file" -- it's a generated file.
It's normally generated by 'flex', which is the GNU version of lex,
during the make process. The source file that it is generated from
is called ada-lex.l, (l for lex), and that file SHOULD be present
in your source (tarball) tree.
However, since some people don't have flex installed, we (the gdb
maintainers) usually go ahead and include ada-lex.c in our source
distribution, just to make things easy. And in fact, you will find
it in our tarball for gdb-6.5 (I hope).
However*2, you are not getting your source tarball from us.
You're getting it from the insight maintainers. And for whatever
reason, they seem to have omitted this file, perhaps assuming that
everyone has flex installed and therefore can generate it.
So there are a number of things you can do at this point.
I can only think of one that would fall under the category
of "supported", though, and that would be --
Install flex.
This is not difficult to do, and you don't even have to be
root to install it somewhere locally.
If you don't want to do that, you could obtain the actual
gdb-6.5 tarball (as opposed to the insight gdb tarball),
unpack it, and copy the file from there into your insight
tree. This SHOULD be ok, but we can't make you any guarantees.
There's always the possibility that their version is different
(but it's highly unlikely).
To be safe, you could diff the two versions of ada-lex.l.
If they are the same, then you are home free.
Michael
-----Original Message-----
From: gdb-owner@sourceware.org on behalf of Joel Brobecker
Sent: Tue 9/19/2006 10:52 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
next reply other threads:[~2006-09-19 21:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 21:38 Ray Duran [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-19 17:54 Ray Duran
2006-09-19 17:59 ` Joel Brobecker
2006-09-19 18:00 ` Daniel Jacobowitz
2006-09-19 18:54 ` Keith Seitz
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=3CE39F664D1EE14293F6923CD00E42C704CD96B3@montremsg32.na.future.ca \
--to=ray.duran@futureelectronics.com \
--cc=Michael.Snyder@palmsource.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