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:49:00 -0000	[thread overview]
Message-ID: <3CE39F664D1EE14293F6923CD00E42C705DDFF45@montremsg32.na.future.ca> (raw)

Hi Joel,

Thanks very much for replying.

I went off on a side project, but I still need to build a gdb.

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)

Thanks,

-Ray

-----Original Message-----
From: Joel Brobecker [mailto:brobecker@adacore.com] 
Sent: Monday, September 18, 2006 10:37 PM
To: Ray Duran
Cc: gdb@sourceware.org
Subject: Re: gdb build error


Ray,

(sorry about the delay - work suddenly became crazy)

> -Yes, I agree that the file probably existed.
> 
> - I am not sure what mirror site I downloaded the file from, but the
> name of 
> the tar is: insight-6.5.tar.bz2.

Have you been able to build GDB since then?

> - I followed the list of configure and build command that I found on
> the eCos page for installing GNU tools. My final application is to use
> eCos on an ARM.

That may be where you got the sources from. I don't know what this
package contains, so it's going to be difficult for me to help you
further. Maybe the people who actually created the tarball might be
able to help you further.

Otherwise, check before doing the configure that this file exists.
Then do the configure, and check again. Then do the build, and check
again. If it disappears during the build as I suspect, then grep
for that filename in the build output - that should give you a good
clue as to what is happening.

As a workaround, you may want to retrieve that file and copy it back
right after the build failed, and then restart the build. That should
work.

Another approach, of course, is to install flex, check out www.gnu.org.

-- 
Joel


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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19 17:49 Ray Duran [this message]
2006-09-19 17:52 ` Joel Brobecker
2006-09-19 19:07   ` Michael Snyder
  -- strict thread matches above, loose matches on Subject: below --
2006-09-19 21:38 Ray Duran
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-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=3CE39F664D1EE14293F6923CD00E42C705DDFF45@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